[
https://issues.apache.org/jira/browse/ZOOKEEPER-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072849#comment-14072849
]
Alexander Shraer commented on ZOOKEEPER-1987:
---------------------------------------------
Hi Patrick,
Client port/adress are now part of the dynamic information that can be changed
by reconfig. Therefore it is removed from the static file (leaving it there
could result in having one port in the static file and another in the dynamic
file).
The dynamic config info is replicated, and it is identical (ignoring delays) in
all servers from the beginning. So all of the servers must among other things
know the client ports of other servers. (Otherwise, suppose the leader would
only know its own port and push out a config - the followers would have to edit
it and merge with their port info, etc., which is probably not safe to do).
>From the config file you have in the last message, it would not be possible
>for the server to know the ports of other servers - only its own. So with
>3.5.0 you have to include the ports when you list the servers.
tickTime=2000
initLimit=10
syncLimit=5
dataDir=./localhost:2182/data
server.1=localhost:3181:4181;2182
server.2=localhost:3182:4182;2183
server.3=localhost:3183:4183;2184
You could include the clientPort line - it doesn't hurt but it would be
redundant and in any case, the server removes it.
> unable to restart 3 node cluster
> --------------------------------
>
> Key: ZOOKEEPER-1987
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1987
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.5.0
> Reporter: Patrick Hunt
> Assignee: Alexander Shraer
> Priority: Blocker
> Fix For: 3.5.0
>
> Attachments: 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)