[ZBX-7119] data collection stops after no data maintenance until configuration cache is updated Created: 2013 Oct 08 Updated: 2017 May 30 Resolved: 2013 Oct 10 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 1.8.18rc1 |
Fix Version/s: | 1.8.19rc1, 2.0.10rc1, 2.1.8 |
Type: | Incident report | Priority: | Major |
Reporter: | Aleksandrs Saveljevs | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | maintenance | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
When a timer process puts a host into maintenance, it updates both configuration cache and database. However, when it takes a host out of maintenance, it only updates the database, so the host remains in no data maintenance from the perspective of configuration cache. So, technically, data collection stops on that host. What saves us, is that host's maintenance status is set back to HOST_MAINTENANCE_STATUS_OFF when configuration cache is synced again and configuration cache update frequency is probably set to a relatively low value in our users' configuration files, so that is probably the reason issue has gone unnoticed until now. |
Comments |
Comment by Aleksandrs Saveljevs [ 2013 Oct 08 ] |
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7119 . |
Comment by Alexander Vladishev [ 2013 Oct 08 ] |
(1) Will be better to move a new iteration into a DCconfig_set_maintenance() function. It will reduce number of locks and will increase a performance. asaveljevs RESOLVED in r39173. sasha CLOSED |
Comment by Alexander Vladishev [ 2013 Oct 10 ] |
(2) Please review my changes in r39217. asaveljevs Looks good. CLOSED. |
Comment by Aleksandrs Saveljevs [ 2013 Oct 10 ] |
Fixed in pre-1.8.19 r39219, in pre-2.0.10 r39222, and in pre-2.1.8 r39223. |