[ZBXNEXT-6144] Zabbix Proxy history handling without 'history on disk' priority Created: 2020 Aug 19  Updated: 2024 Oct 22  Resolved: 2024 Feb 28

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P)
Affects Version/s: 3.0.31, 4.0.24rc2, 5.0.3rc2, 5.2.0alpha1
Fix Version/s: 7.0.0alpha3, 7.0 (plan)

Type: Change Request Priority: Trivial
Reporter: Edgar Akhmetshin Assignee: Andris Zeila
Resolution: Fixed Votes: 9
Labels: MySQL, Oracle, PROXY, PostgreSQL, partitioning
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PNG File Screenshot 2022-06-24 at 20.45.54.png     PNG File image-2023-07-12-13-06-47-681.png     PNG File screenshot-1.png    
Issue Links:
Causes
causes ZBX-25024 Sender data file does not work with P... Closed
causes ZBX-23896 Proxy complaining about unexpected fi... Closed
Duplicate
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ZBXNEXT-8568 Update template to support changes Change Request (Sub-task) Closed Denis Rasikhov  
Epic Link: Zabbix 7.0
Team: Team A
Sprint: Sprint 100 (May 2023), Sprint 101 (Jun 2023), Sprint 102 (Jul 2023), Sprint 103 (Aug 2023), Sprint 104 (Sep 2023), Sprint 105 (Oct 2023), Sprint 106 (Nov 2023)
Story Points: 10

 Description   

Current Proxies clones Server behaviour:

  • get value in buffer
  • store value in database
  • read value
  • sync value
  • delete value

The problem:

  • DELETE .. IN () .. - happens with a housekeeper - making proxy stuck on receiving new values;

Feature request:

  • get value in cache;
  • sync value;
  • drop value from cache if sync is successful;
  • store value if sync failed up to offline buffer max;
  • store value if online buffer is activated;
  • backlog sync on network recovery with further drop of the database partitions used to store backlog;

Or even simplier - dump json files which can be uploaded back and removed as needed for offline buffer.



 Comments   
Comment by Vladislavs Sokurenko [ 2020 Aug 20 ]

It is not related to housekeeping but receiving of new configuration where lots of items got deleted:

delete from items where (itemid in (4445395,4445396,4445397,4445398,4445399,4445401,4445402,4445403,4445404,4445405,4445406,4445407,4445408,4445409,4445410,4445411,4

Could you please provide more information on what is happening, are you trying to remove lots of items from Zabbix proxy ?

Perhaps bulk deletion should be implemented to avoid huge queries.

Could be caused by ZBX-13266, see recommended limits

Comment by Vladislavs Sokurenko [ 2023 Apr 25 ]

What kind of queries are slow ?

Comment by Vladislavs Sokurenko [ 2023 Jul 14 ]

Implemented in:

  • 7.0.0alpha3 (master) 55d41231c96
  • pre-7.0.0beta2 22783668d31, 9f0d95d1f12
Comment by Martins Valkovskis [ 2023 Jul 19 ]

Updated documentation:

Comment by LivreAcesso.Pro [ 2023 Jul 31 ]

Please, backport this to 6.0.x versions.

Generated at Tue Apr 15 09:45:57 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.