[ZBXNEXT-4894] Improve throttling by using md5 hash Created: 2018 Nov 30  Updated: 2024 Apr 10  Resolved: 2019 Jan 16

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: 4.2.0alpha3, 4.2 (plan)

Type: Change Request Priority: Major
Reporter: Vladislavs Sokurenko Assignee: Andrejs Sitals
Resolution: Won't fix Votes: 0
Labels: performance, preprocessing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Sub-task
depends on ZBXNEXT-4724 Advanced preprocessing: validation an... Closed
Team: Team A
Team: Team A
Sprint: Sprint 49 (Feb 2019)
Story Points: 0.5

 Description   

Value throttling is added in ZBXNEXT-4724, however it means that preprocessing manager now sends historical values to workers so that they can compare new data with old and if nothing has changed then value must be throttled. The problem is that it can be large amounts of data sent to the workers and back. It should be considered to send only md5 hash to avoid moving large amounts of data and thus improving performance of preprocessing manager due to sending less data and calculating hash in workers.



 Comments   
Comment by Andrejs Sitals [ 2019 Jan 16 ]

MD5 hash alone can't be used for comparing values, as it is possible to create collisions which would result in discarding a value that has changed. Depending on usage of monitoring/throttling, this can be a security threat.

Comment by Vladislavs Sokurenko [ 2019 Jan 16 ]

OK, thanks ! Closing as Won't Fix

Generated at Thu Apr 18 19:29:46 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.