[ZBX-13396] Timer process can lock items and keep locks long time Created: 2018 Jan 25  Updated: 2024 Apr 10  Resolved: 2018 Jul 19

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 3.0.14, 3.4.6
Fix Version/s: 4.0.0alpha9, 4.0 (plan)

Type: Problem report Priority: Minor
Reporter: Alexey Pustovalov Assignee: Andris Zeila
Resolution: Fixed Votes: 0
Labels: history, timer, trigger
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File hc_triggers.diff    
Issue Links:
Causes
causes ZBX-14818 Zabbix Server Crash Closed
Duplicate
Team: Team A
Sprint: Sprint 26, Sprint 27, Sprint 28, Sprint 29, Sprint 30, Sprint 31, Sprint 32, Sprint 33, Sprint 34, Sprint 35, Sprint 36, Sprint 37, Sprint 38
Story Points: 7

 Description   

Steps to reproduce:
1. Create a lot time-based nodata triggers
2. Create many regular items without triggers
3. Simulate when timer process has to check time-based nodata triggers and spend some time to do that.
4. When history cache will have 1000+ values for items from these nodata triggers, history syncer misses such values, because they are locked by timer. It will not process next values till timer will free items from nodata triggers.

 Comments   
Comment by MATSUDA Daiki [ 2018 Jul 10 ]

It is better that sync_server_history() and sync_proxy_history to static.

vso thank you ! will be fixed under ZBXNEXT-413

Generated at Thu Apr 25 03:47:02 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.