[Spread-users] updating a spread configuration
yairamir at cnds.jhu.edu
Thu Jan 9 11:51:56 EST 2003
The old daemons will not experience a problem, but will not
be willing to talk with the new daemons before you change their
configuration and restart.
The new daemons may experience a problem because they will hear the
old daemons but the old daemons would not talk with them.
It will be more serious if part of the old daemons will be restarted
but not all of them - then, nothing will actually work.
Currently Spread does not support adding to the configuration without
restarting the daemons. It is doable to add it although not very
simple. We know about this issue.
Jeremy> We have a spread cluster in configuration that we need to upgrade. We
Jeremy> want to add several new machines to the cluster. Is it possible to do
Jeremy> this without interrupting the currently running daemons?
Jeremy> The current configuration file doesn't say anything about the new
Jeremy> machines. So at some point we'll need to change the configuration for
Jeremy> the running daemons and restart them. Do we need to do this before
Jeremy> starting up the new daemons or can we do it afterwards?
Jeremy> I recall that spread prints a warning message when it receives a
Jeremy> message from a daemon that isn't in its configuration. (I've run into
Jeremy> this situation when a couple developers in our office were running
Jeremy> daemons for testing.) Does this warning indiciate a more serious
Jeremy> Spread-users mailing list
Jeremy> Spread-users at lists.spread.org
More information about the Spread-users