Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #1410] Race condition when issueing multiple reloads results in hanging IDO2DB processes #614

Closed
icinga-migration opened this issue Apr 18, 2011 · 5 comments
Milestone

Comments

@icinga-migration
Copy link

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

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
@icinga-migration
Copy link
Author

Updated by mfriedrich on 2011-04-28 10:17:16 +00:00

  • Status changed from New to Feedback
  • Priority changed from High to Normal

a bit more feedback like debug logs would be much appreciated.

i've played around it, and added one for myself.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2011-04-28 10:40:36 +00:00

  • File added ido2db_pid5020_n_core_sighup.txt.tar.gz

@icinga-migration
Copy link
Author

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

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2011-04-28 20:29:10 +00:00

  • Done % changed from 60 to 100

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2011-05-02 15:58:01 +00:00

  • Category set to Other
  • Status changed from Feedback to Resolved

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant