[
https://issues.apache.org/jira/browse/ZOOKEEPER-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073753#comment-14073753
]
Hongchao Deng commented on ZOOKEEPER-1987:
------------------------------------------
[~shralex]
My first thought is that it's a little ambiguous to put version under the
server list. It's best to give reusable config file. A version and other info
could be separated.
> Storing the version in a separate file creates a problem of keeping this file
> in sync with the dynamic config file.
It's doable. A server can hold acking back until files are finished. And it
takes the final written file as a flag. Anyway, it's a bit of work but doable.
> unable to restart 3 node cluster
> --------------------------------
>
> Key: ZOOKEEPER-1987
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1987
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Affects Versions: 3.5.0
> Reporter: Patrick Hunt
> Assignee: Alexander Shraer
> Priority: Blocker
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1987-ver1.patch, ZOOKEEPER-1987-ver2.patch,
> ZOOKEEPER-1987-ver3.patch, ZOOKEEPER-1987.patch, f1.jstack, l3.jstack,
> test3.tar.gz
>
>
> I tried a fairly simple test, start a three node cluster, bring it down, then
> restart it. On restart the servers elect the leader and send updates, however
> the negotiation never completes - the client ports are never bound for
> example.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
