[
https://issues.apache.org/jira/browse/ZOOKEEPER-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857511#comment-13857511
]
Alexander Shraer commented on ZOOKEEPER-1691:
---------------------------------------------
Hi Helen,
Sorry for the delay. Here are a few remaining comments:
1) Please make sure that edge cases work properly. For example, after starting
2 servers with standaloneEnabled = true I am able to remove one of them. Please
try to run other edge cases.
2) When I'm trying to remove all servers I get a No Quorum Connected error
instead of "BadArguments" error that was issued previously. This is because the
check for number of servers < 2 in PrepRequestProcessor is now gone. I think
there should still be a check there, perhaps taking into account the new flag.
Best Regards,
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.5#6160)
