[
https://issues.apache.org/jira/browse/ZOOKEEPER-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113142#comment-17113142
]
kaushik srinivas commented on ZOOKEEPER-3842:
---------------------------------------------
Hi [~symat]
Thanks a lot for the response, will comment on PR for further queries.
So as of now, we can confirm that with 3.5.7 or even latest version of ZK,
rolling scale out is impossible.
The only way out is to use dynamic reconfig feature and do the scale out of the
cluster right ?
Thanks,
kaushik
> Rolling scale up of zookeeper cluster does not work with reconfigEnabled=false
> ------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-3842
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3842
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum, server
> Affects Versions: 3.5.7
> Reporter: kaushik srinivas
> Assignee: Mate Szalay-Beko
> Priority: Blocker
> Labels: features
>
> With
> *reconfigEnabled = false (not explicitly setting, relying on the default
> value).*
>
> Install 3 zookeeper servers with 3 zk information in all the 3 zookeeper
> quorum servers.
>
> Do a rolling scale up of cluster from 3 to 5 with below steps.
>
> 1. Install 4th zookeeper with servers list of 1,2,3,4,5
> 2. Install 5th zookeeper with servers list of 1,2,3,4,5
> 3. Do a rolling restart of servers 1 2 & 3 with servers list of 1,2,3,4,5.
>
> Result/Behavior: quorum is lost.
>
> With this https://issues.apache.org/jira/browse/ZOOKEEPER-2819
> description points at a PR [https://github.com/apache/zookeeper/pull/292]
> which should have this issue of rolling restart fixed without dynamic
> reconfiguration feature enabled.
>
> We still see quorum loss issues without dynamic reconfig feature enabled.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
