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
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Assignee: mfriedrich
Status: Resolved (closed on 2011-05-02 15:58:01 +00:00)
Target Version: 1.4
Last Update: 2011-05-02 15:58:01 +00:00 (in Redmine)
There seems to be a race condition when sending SIGHIP to an Icinga process already busy with an ongoing reload. It's pretty easy to reproduce, just launch a few consecutive reloads. You will quickly remain with multiple ido2db childs and therefore be in trouble.
idoutils: non-blocking icinga core while config dump at startup to ido2db #866 fix race condition when issueing multiple reloads results in hanging IDO2DB processes #1410
check the issues for more information.
https://dev.icinga.org/issues/866
https://dev.icinga.org/issues/1410
refs #866
refs #1410
The text was updated successfully, but these errors were encountered:
Updated by mfriedrich on 2011-04-28 10:52:07 +00:00
Assigned to set to mfriedrich
Target Version set to 1.4
Done % changed from 0 to 60
ok, fixed that within the commit for #866 when rewriting the dynamic buffer to a worker thread in ido2db, not blocking the core anymore.
that commit is running in a productive environment by a user, so i consider a bit more cpu usage in the first place a good achievement for fixing this issue and resolving #866
This issue has been migrated from Redmine: https://dev.icinga.com/issues/1410
Created by tgelf on 2011-04-18 09:00:01 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2011-05-02 15:58:01 +00:00)
Target Version: 1.4
Last Update: 2011-05-02 15:58:01 +00:00 (in Redmine)
There seems to be a race condition when sending SIGHIP to an Icinga process already busy with an ongoing reload. It's pretty easy to reproduce, just launch a few consecutive reloads. You will quickly remain with multiple ido2db childs and therefore be in trouble.
Attachments
Changesets
2011-04-28 10:52:39 +00:00 by mfriedrich 39fa0ac
The text was updated successfully, but these errors were encountered: