On 11.02.2014 11:26, Carlos Cesario wrote:


One question.
Why the all services in icinga-node-2 remain "ONLINE" ?  Shouldn't
these services switch to offline too?!
I'm not sure what you mean with the term "online" and "offline".
Depending on the check authority, those checks being executed on the
secondary node will stay in the same state as before and once the
cluster connection is re-established, the check history will be
synchronized from b->a again.
I mentioned "online" and "offline" making reference a cluster and
services states.
If you got any better idea feel free to propose/discuss. One of our
ideas, which does not really work, was the following:

a   ----------------------X---------------> b
freshness triggers                       normal check
result is stale, not-ok                  check result, history
....                                     ....
     <-------connection re-established----->
history out-of-sync                      history-out-of-sync


So that way won't work very well unless you don't are about somewhat
mixed/merged history and other strange effects.

A different approach could be a special state type (or field) for
clustering the service, and based on its authority compared to the
current cluster state, it may tell that the current result is stale
because the node is down (but that would rather be a ui feature then).

I agree with you, maybe  a new state, or a flag indicating that all
hosts/services from that cluster is down or disconnected or pending.

See my example, I turn off my checker node yesterday (10/02/2014 - at
around 18:00), and all services remain "OK" (last status).

Would be interesting anythink to "flag" it.

I'll discuss it with Gunnar and the team. It's actually a good point, as none of the current interfaces could reflect that in a correct manner, independant of statusdat/ido/livestatus/whateverfuturebackend.

https://dev.icinga.org/issues/5636

Kind regards,
Michael


--
DI (FH) Michael Friedrich

michael.friedr...@gmail.com  || icinga open source monitoring
https://twitter.com/dnsmichi || lead core developer
dnsmi...@jabber.ccc.de       || https://www.icinga.org/team
irc.freenode.net/icinga      || dnsmichi

_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to