[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845778#comment-13845778
 ] 

Alexander Shraer commented on ZOOKEEPER-1691:
---------------------------------------------

Hi Bruno,

thanks for testing this. I have a feeling that your findings are not specific 
to the current JIRA but more general about dynamic reconfig.
The current JIRA should have effect when your start or end configuration 
contains just a single server, which is not the case in your scenario - you 
start from 2 servers and are going to 3. Its possible of course that the patch 
has effect there but you should run your scenario with and without the patch to 
verify.

The problem that your log shows is that the starting config of server 3 
includes only this server. Since the standaloneEnabled flag is false, this 
server happily forms an ensemble just by himself, and doesn't know that you've 
issued a reconfig. This works as expected.
You should start it with a config including all three servers (the general rule 
of thumb for joiner's A config should be current config + A).
You can see that the other servers do add it to the configuration, so the 
reconfig worked. They just think server 3 is faulty (and don't mind because one 
out of three can fail).

About the renaming - could you please open a JIRA for this and perhaps propose 
a patch ? I'm a bit concerned what will happen if there's a failure after you 
deleted the current config file but before you renamed. 

Thanks again for taking a look at this,
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)

Reply via email to