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
Assignee: mfriedrich
Status: Resolved (closed on 2015-03-19 17:05:03 +00:00)
Target Version: 2.3.3
Last Update: 2015-03-19 17:05:03 +00:00 (in Redmine)
Icinga Version: v2.3.0-11-g8682c53
Backport?: Not yet backported
Include in Changelog: 1
Required changes
There's a bit more outdated stuff inside, and some sections in the general docs require updates as well.
Original description
In the section "Asynchronous Event Execution" as part of the chapter "Migration" it is stated that Icinga2 does not block when a check is being executed while at the same time it is stated that events and notifications each run in their own thread. (Utilizing the term "asynchronous" in both cases.) This is very likely causing the reader to think that Icinga2 spawns a new thread for each executed check, which it does not.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/8764
Created by jmeyer on 2015-03-16 13:59:00 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2015-03-19 17:05:03 +00:00)
Target Version: 2.3.3
Last Update: 2015-03-19 17:05:03 +00:00 (in Redmine)
Required changes
There's a bit more outdated stuff inside, and some sections in the general docs require updates as well.
Original description
In the section "Asynchronous Event Execution" as part of the chapter "Migration" it is stated that Icinga2 does not block when a check is being executed while at the same time it is stated that events and notifications each run in their own thread. (Utilizing the term "asynchronous" in both cases.) This is very likely causing the reader to think that Icinga2 spawns a new thread for each executed check, which it does not.
Changesets
2015-03-19 17:03:01 +00:00 by (unknown) 0c0bae2
2015-03-19 17:03:48 +00:00 by (unknown) df99eab
The text was updated successfully, but these errors were encountered: