You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MySQL increases the value of auto increment by every single ON DUPLICATE KEY UPDATEor REPLACE query.
Due to this, you can easily hit the auto increment max value.
So, i would recommend to truncate the prefix_hoststatus and prefix_servicestatus tables on every restart of the monitoring core, inside of the FINISH_OBJECT_DUMP event handler...
MySQL increases the value of auto increment by every single
ON DUPLICATE KEY UPDATE
orREPLACE
query.Due to this, you can easily hit the auto increment max value.
So, i would recommend to truncate the prefix_hoststatus and prefix_servicestatus tables on every restart of the monitoring core, inside of the FINISH_OBJECT_DUMP event handler...
See: https://www.percona.com/blog/2011/11/29/avoiding-auto-increment-holes-on-innodb-with-insert-ignore/
This is an example of a system with 60 services.
![example](https://user-images.githubusercontent.com/9019992/27794935-7865d75c-6004-11e7-9e2b-f894ae138ab7.png)
Patch
The text was updated successfully, but these errors were encountered: