GitHub user hanm opened a pull request:
https://github.com/apache/zookeeper/pull/292
ZOOKEEPER-2819:Changing membership configuration via rolling restart â¦
â¦does not work on 3.5.x.
This patch disables the creation of dynamic config files (zoo.cfg.dynamic)
and static config back up files (zoo.cfg.bak) when the dynamic reconfig feature
flag (reconfigEnabled) is disabled. With this patch the membership information
(such as server list) will be stored in static zoo.cfg file and such
information would not go through quorum and leader / follower sync phase, which
makes it possible for users to continue using the old rolling restart approach.
@shralex PTAL.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hanm/zookeeper ZOOKEEPER-2819
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/292.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #292
----
commit 896ee06502d602ea5147d489a5e6f777fbaaa83e
Author: Michael Han <[email protected]>
Date: 2017-06-26T22:41:26Z
ZOOKEEPER-2819:Changing membership configuration via rolling restart does
not work on 3.5.x.
This patch disables the creation of dynamic config files (zoo.cfg.dynamic)
and static config back up files (zoo.cfg.bak) when the dynamic reconfig feature
flag (reconfigEnabled) is disabled. With this patch the membership information
(such as server list) will be stored in static zoo.cfg file and such
information would not go through quorum and leader / follower sync phase, which
makes it possible for users to continue using the old rolling restart approach.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
