Team A
[ZBX-14821] Unnecessary idle time between timer trigger processing in history syncer Created: 2018 Sep 06 Updated: 2024 Apr 10 Resolved: 2018 Oct 15 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 4.0.0beta1 |
| Fix Version/s: | 4.0.0beta2, 4.0 (plan) |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Andris Zeila | Assignee: | Andris Zeila |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Team: | Team A |
| Team: | Team A |
| Sprint: | Sprint 42, Sprint 43, Sprint 44, Sprint 45 |
| Story Points: | 0.5 |
| Description |
|
When there are no history data to process (history cache is empty), but there are a 500+ timer triggers in queue, history syncer will process 500 timer triggers and enter idle state for 1 sec instead of immediately processsing the next batch of timer triggers. |
| Comments |
| Comment by Andris Zeila [ 2018 Sep 13 ] |
|
Released in:
|
| Comment by Alexander Vladishev [ 2018 Sep 13 ] |
|
(6) [D] Documentation needs to be updated martins-v sasha, could you clarify what to document here? I was speaking to wiper about it and we could not figure out. The main change of timer triggers processed by history syncers is documented. sasha Тhe output of the "history syncer" process has changed. This must be documented. Before this fix: zabbix_server: history syncer #4 [synced 35 items in 0.166198 sec, idle 5 sec] After: zabbix_server: history syncer #3 [processed 0 values, 0 triggers in 0.000005 sec, idle 1 sec] martins-v Updated:
RESOLVED sasha CLOSED |
| Comment by richlv [ 2018 Oct 13 ] |
|
Alexander, thank you so much for the attention to the detail. Highly appreciated. |