[
https://issues.apache.org/jira/browse/ZOOKEEPER-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787961#comment-13787961
]
Alexander Shraer commented on ZOOKEEPER-1691:
---------------------------------------------
I've verified that at least part of the problem is that both the established
leader and the joining server have configuration version equal to 0, so the
leader can't convince the joiner to adapt the current config. I'm working on
this.
In the meanwhile, here's a workaround: remove your change to FastLeaderElection
and add this dummy reconfiguration (just to bump up the version) before you add
the two servers:
reconfigServers.clear();
reconfigServers.add(serverStrings.get(leaderId) + "\n");
testReconfig(leaderId, true, reconfigServers);
With this change adding the two servers in your test works for me. The bad news
is that when the test shuts down the leader the remaining servers can't form a
quorum for some reason.
> Add a flag to disable standalone mode
> -------------------------------------
>
> Key: ZOOKEEPER-1691
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1691
> Project: ZooKeeper
> Issue Type: Improvement
> Components: quorum
> Reporter: Michi Mutsuzaki
> Assignee: Helen Hastings
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1691.patch, ZOOKEEPER-1691.patch,
> ZOOKEEPER-1691.patch, ZOOKEEPER-1691.patch, ZOOKEEPER-1691.patch
>
>
> Currently you cannot use dynamic reconfiguration to bootstrap zookeeper
> cluster because the server goes into standalone mode when there is only one
> server in the cluster.
> --Michi
--
This message was sent by Atlassian JIRA
(v6.1#6144)
