Closed icinga-migration closed 11 years ago
Updated by mfriedrich on 2012-05-05 11:41:42 +00:00
Updated by mopp on 2012-08-08 13:24:43 +00:00
I ran into the same problem described here [[http://www.monitoring-portal.org/wbb/index.php?page=Thread&threadID=25711]] The result is ido2db uses 100% CPU Setting enable_sla=0 in ido2db.cfg fixed the problem. The problem seems to start when the table slahistory gets too big.
In the ido2db log files you see queries like this which took very long time. The result was the Icinga deamon was not able to communicate with ido2db, because it is busy.
SELECT slahistory_id, UNIX_TIMESTAMP(start_time) AS start_time, UNIX_TIMESTAMP(end_time) AS end_time, UNIX_TIMESTAMP(acknowledgement_time) AS acknowledgement_time, state, state_type, scheduled_downtime FROM icinga_slahistory WHERE instance_id = '1' AND object_id = '426' AND ((start_time > FROM_UNIXTIME(1343826917) AND start_time < FROM_UNIXTIME(1344845700)) OR (end_time > FROM_UNIXTIME(1343826917) AND end_time < FROM_UNIXTIME(1344845700)) OR (start_time < FROM_UNIXTIME(1343826917) AND end_time > FROM_UNIXTIME(1344845700)) OR (end_time IS NULL))
Updated by mfriedrich on 2012-08-31 16:48:30 +00:00
Updated by mfriedrich on 2012-11-06 14:04:55 +00:00
Updated by mfriedrich on 2012-11-06 14:05:32 +00:00
Updated by mfriedrich on 2012-11-21 12:40:20 +00:00
Updated by mfriedrich on 2012-11-21 12:43:13 +00:00
enable_sla will be deprecated in 1.9 due to the performance problems, as well as their missing use cases.
Updated by mfriedrich on 2014-12-08 14:37:41 +00:00
This issue has been migrated from Redmine: https://dev.icinga.com/issues/2550
Created by mfriedrich on 2012-04-25 10:39:31 +00:00
Assignee: (none) Status: Closed (closed on 2012-11-21 12:40:20 +00:00) Target Version: (none) Last Update: 2014-12-08 14:37:41 +00:00 (in Redmine)
happen too often lately.
http://www.monitoring-portal.org/wbb/index.php?page=Thread&threadID=25711 http://www.monitoring-portal.org/wbb/index.php?page=Thread&threadID=25397