zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Han <h...@cloudera.com>
Subject Re: How to add nodes to a Zookeeper 3.5.3-beta ensemble with reconfigEnabled=false
Date Wed, 21 Jun 2017 19:20:31 GMT
You can still do rolling restarts for 3.5.x including 3.5.3-beta. Rolling
restart requires edits the zoo.cfg - the static configuration files,
instead of zoo.cfg.dynamic.x, which is the dynamic reconfiguration file
that stores reconfig parameters. This dynamic config file is managed by ZK
and is not supposed to be edited by users directly. See
reconfig_file for more details.

Another option is to use dynamic reconfig through command line, the doc
linked above should provide enough information to get started.

On Wed, Jun 21, 2017 at 11:33 AM, Guillermo Vega-Toro <gvegator@us.ibm.com>

> Hi,
> I have a 3-node Zookeeper 3.5.3-beta ensemble. This was initially created
> by un-taring the Zookeeper tarball into 3 machines, editing the zoo.cfg
> file with the 3 server entries, and starting the servers. The ensemble
> started, and a zoo.cfg.dynamic.100000000 file was created with the
> server.x lines in all servers.
> Now, I want to add 2 more nodes to grow to a 5-node ensemble. In Zookeeper
> 3.4.6, I would install the two new nodes, update the zoo.cfg files on all
> servers to add the new nodes, and restart the servers one by one. But in
> version 3.5.3-beta, this is not possible - any changes made to
> zoo.cfg.dynamic.100000000 are ignored, even if reconfiguration is
> disabled. If the dynamic config file is modified to add new servers and
> the server is restarted, the dynamic config file gets overwritten with the
> old 3-node configuration when the server starts.
> So, it looks like in Zookeeper 3.5.x, the way to add nodes is to use the
> new reconfig command on the CLI. But if the reconfiguration feature is
> disabled for security reasons (as it is in 3.5.3-beta by default), then
> adding nodes "the old way" by editing the config file and restarting the
> servers is not possible either. Does this mean that in Zookeeper
> 3.5.3-beta, in order to grow the ensemble, it is necessary to enable
> reconfiguration (by setting reconfigEnabled=true in zoo.cfg and restarting
> all servers), then running the CLI to add the new nodes? Then after the
> new nodes are added, edit zoo.cfg to disable reconfiguration on all
> servers, and restart all servers again?
> Thanks


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message