[
https://issues.apache.org/jira/browse/ZOOKEEPER-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073630#comment-14073630
]
Hongchao Deng commented on ZOOKEEPER-1987:
------------------------------------------
hey [~shralex]. Thanks for sharing. Preserving backward compatibility
definitely makes the project harder to maintain. However, it encourages people
to try 3.5.x without being stopped at the start. So it's good to support that :)
Moreover, I am wondering what the version in dynamic file is? Is it helping to
locate the reconfig command more quickly? Or just a notion of version..
I thought about the dynamic file again carefully and had a second thought on
this:
https://medium.com/@hdeng/zookeeper-dynamic-config-file-b7557a2fb42f
Basically, I am suggesting:
1. separate the version (zxid) to another files.
2. Append a sequential number to the filename in backup.
3. backup should be an optional argument (e.g. a directory maybe?). This would
be nice to separate production and testing environment.
Please take a moment to review the ideas and share your feedback here.
> 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)
