This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
[dev.icinga.com #3159] core: log a message when reaper max time is reached #1113
Labels
Milestone
This issue has been migrated from Redmine: https://dev.icinga.com/issues/3159
Created by mfriedrich on 2012-09-22 15:27:18 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2012-09-25 13:10:10 +00:00)
Target Version: 1.8
Last Update: 2012-09-25 13:10:10 +00:00 (in Redmine)
discussed that with tom gelf, and we came to the conclusion, that reaching the max time for the reaper itsself and the core bailing out of reaping is rather servere in performance regards. this is due to the fact that the core cannot process the already stashed checkresults queue properly, and having problems to stash even more checkresults being read from disk over there. the root cause for that could be more than just a slow core - but it will of course increase latency, or even 100% cpu load and unresponsible cores.
so in order to stay sane, at least log a message (and not only debug message), to inform the user and point to some performance tuning tips too.
Changesets
2012-09-23 09:34:00 +00:00 by mfriedrich 50c70c6
Relations:
The text was updated successfully, but these errors were encountered: