It is pretty easy to do by hand and is pretty easy to script (it was for
us).
The process for adding is
a) configure and start a new node
b) re-configure and restart each existing node in turn to know about the new
node
you now have a larger cluster.
To drop a node,
a) reconfigure and
I would prefer not restarting. Start/Stop the new/old process and then start
a round of consensus for adding/removing a machine. I guess if one can do
that then there is stopping of process required. Am I missing something
here?
A
On Thu, Nov 5, 2009 at 11:14 AM, Ted Dunning
You have two options.
What Henry is talking about is a sophisticated update to ZK internals that
does a very nice job of handling all the possible split-brain issues and
other pathologies that can result from growing or shrinking a cluster. His
patch isn't ready yet, but when it is, it should be
Ah. Sorry. But I got it. I guess what Henry is working on is what I am
looking for.
Thanks
A
On Thu, Nov 5, 2009 at 11:32 AM, Ted Dunning ted.dunn...@gmail.com wrote:
You have two options.
What Henry is talking about is a sophisticated update to ZK internals that
does a very nice job of
Hi -
Yes there are future plans. See
https://issues.apache.org/jira/browse/ZOOKEEPER-107. I have code written for
this that works but is not rock-solid yet.
cheers,
Henry
On Thu, Nov 5, 2009 at 11:02 AM, Avinash Lakshman
avinash.laksh...@gmail.com wrote:
Hi All
Is it possible to remove
Hi All
Is it possible to remove nodes and add nodes dynamically to the ZK cluster
via API? Any plans in the future to do this?
TIA
A
Apologies for the late notice, but I wanted to advertise a pair of short
talks by Mahadev and myself at the Hadoop Meetup tonight in Oakland:
Mahadev will be giving a broad overview of ZooKeeper and talking about its
uses inside and outside of Yahoo!, and I will be talking about upcoming
features
