Justin SB created ZOOKEEPER-1727:
------------------------------------
Summary: Doc request: The right way to expand a cluster
Key: ZOOKEEPER-1727
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1727
Project: ZooKeeper
Issue Type: Wish
Affects Versions: 3.5.0
Reporter: Justin SB
Priority: Minor
When expanding a cluster from 2->3, if ZK server #3 isn't up yet, then it seems
that the reconfig request times out with a connection-loss error. The
configuration is updated though. So we could wait, reconnect, and then refetch
the config to make sure we did join the quorum, though that seems a little bit
hacky!
What is correct way to do this (and cluster growth in general)? Should we
bring up new ZK servers before issuing the reconfig command? What is the right
way to bring up new ZK servers (connect as a client, request the config, save
the config to the zk.conf.dynamic file, add our new server line to the new
zk.conf.dynamic file, start the new server, call reconfig as a client to the
existing cluster)?
Is this documented anywhere? (Just the steps to do it "the right way" would be
great, no need for actual code) :-)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
