[
https://issues.apache.org/jira/browse/ZOOKEEPER-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Shraer updated ZOOKEEPER-2819:
----------------------------------------
Summary: Changing configuration via rolling restart does not work on 3.5.x.
(was: Rolling restarts does not work on 3.5.x.)
> Changing configuration via rolling restart does not work on 3.5.x.
> ------------------------------------------------------------------
>
> Key: ZOOKEEPER-2819
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2819
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum, server
> Affects Versions: 3.5.0, 3.5.1, 3.5.2, 3.5.3
> Reporter: Michael Han
> Priority: Critical
>
> In 3.5.x there is no easy way of doing the rolling restarts because of the
> introduction of dynamic reconfig feature in ZOOKEEPER-107, which prevents
> direct manual editing of zoo.cfg file.
> ZOOKEEPER-2014 introduced a reconfigEnabled flag to turn on / off the
> reconfig feature. We can use same flag and when it sets to false, it should
> disable both in memory and on disk updates for config files, besides
> disabling the reconfig commands on CLI which ZOOKEEPER-2014 already did, so
> users can continue using rolling restarts if needed.
> We should also document explicitly the support of rolling restarts will be
> deprecated at what release time frame and promote reconfig as the replacement.
> The problem was raised at user mailing list by Guillermo Vega-Toro, reference
> thread:
> http://zookeeper-user.578899.n2.nabble.com/How-to-add-nodes-to-a-Zookeeper-3-5-3-beta-ensemble-with-reconfigEnabled-false-td7583138.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
