[
https://issues.apache.org/jira/browse/ZOOKEEPER-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112492#comment-14112492
]
Hongchao Deng commented on ZOOKEEPER-2000:
------------------------------------------
I looked at a few other testPortChange failures and they have something in
common -- they all failed in changing the leader's port, which enforces another
leader election.
[~shralex] Does the completion of reconfig guarantee that a new leader having
been elected?
> Fix ReconfigTest.testPortChange
> -------------------------------
>
> Key: ZOOKEEPER-2000
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2000
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Affects Versions: 3.5.0
> Reporter: Alexander Shraer
> Assignee: Alexander Shraer
> Priority: Minor
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-2000.patch, ZOOKEEPER-2000.patch
>
>
> testPortChange changes all ports and role of the server and thus
> causes existing clients to disconnect, while this wouldn't happen if only the
> client port changes. Need to fix it to only change client port and not all
> the other parameters and make sure that the clients don't disconnect, while
> new clients shouldn't be able to connect to the old port.
--
This message was sent by Atlassian JIRA
(v6.2#6252)