[
https://issues.apache.org/jira/browse/ZOOKEEPER-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846973#comment-13846973
]
Alexander Shraer commented on ZOOKEEPER-1691:
---------------------------------------------
Hi Bruno,
standaloneEnabled=false seems correct. Otherwise you would not be able to
connect the servers since each of them would form a separate standalone
ensemble. The fact that server 2's line disappears initially from its own
config is expected - once it syncs with the leader it adopts the current config
in which its not yet a member. the initial config you start it with is invalid
and only used to bootstrap server 2. Its sort of a hack, I agree, but we need
to tell it which ports to listen to initially, etc.
The error messages may indicate a bug or two. The second one from server 2
means that its trying to initiate a connection to itself, which I don't think
should happen. The fix for this seems easy. I'm not sure about the reason for
server 1's error message. In any case, would be great if you open a JIRA for
this, you can assign it to me.
Thanks,
Alex
> 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,
> ZOOKEEPER-1691.patch, test scenario.txt
>
>
> 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.4#6159)
