Updates:
Status: NeedFeedback
Owner: ---
Labels: -Type-Defect -Component-mond Type-Enhancement
Comment #6 on issue 1126 by [email protected]: ganeti-mond and ganeti-confd
fail to start upon node add
https://code.google.com/p/ganeti/issues/detail?id=1126
The above patch removes the startup errors for the monitoring daemon;
this makes sense as the daemon is explicitly started at node addition.
The configuration daemon, however, is not start by the node addition
procedure;
it will eventually be started by the watcher. Given that the confd protocol
involves asking all master candidates, that delay (up to 5 minutes) seems
acceptable to still provide a reliable enough service. Of course, we could
change it and start confd directly at node addition (providing all
information
it needs in the initial data). It is a design decision if we want to do
this.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
