Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #1741] do not update host/service status during scheduler initialization on startup #691
This issue has been migrated from Redmine: https://dev.icinga.com/issues/1741
Created by mfriedrich on 2011-07-22 16:01:07 +00:00
this might be interferring with the config dump (as the status update queries are huge, the amount of data being sent over the socket is taking ages for idomod too).
so this is something within the core probably, but the main cause in idoutils as integrated neb module.
attached is a file showing all queries on startup.
2011-07-22 16:54:16 +00:00 by mfriedrich 2bd6dcc
Updated by mfriedrich on 2011-07-22 16:52:25 +00:00
it's triggered by events on newly added hosts and services, which get added to the scheduling queue. this happens way before the event loop for monitoring really started.
Updated by mfriedrich on 2011-07-22 16:53:37 +00:00
Updated by mfriedrich on 2011-07-29 14:58:56 +00:00
i consider it unneeded updates during the overal config dumping. a host/service state from the last cycle will be kept within the database itsself - and even if you could still re-enable the retained state dumpings. so this is the wrong location in order to fix that, removing it for further performance increasements, especially on startup.