-
Notifications
You must be signed in to change notification settings - Fork 333
Description
I set up an HA configuration with a master and a spare Shinken. On each server I set up the MongoDB scheduler retention module and the WebUI module.
When I stop the main Shinken, the configuration is pushed to the spare Shinken, the retention objects are loaded in the Mongo DB and populated to the spare broker and WebUI.
Everything is fine except for the daemons states broks that are not received by the main broker !
As of it the regenerator does not maintain the main Shinken daemon states, whereas they are maintained by the spare broker. It does not seem to be a problem because everything seems ok, the checks are executed, but I am not sure there is not any unpredictable side effects ...
Shinken daemons states on the main Shinken WebUI:
We should see that all daemons are alive...