[jira] [Commented] (ZOOKEEPER-2137) Make testPortChange() less flaky

["Flavio Junqueira (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245225#comment-15245225 ] 

Flavio Junqueira commented on ZOOKEEPER-2137:
---------------------------------------------

The fix committed apparently didn't fix it:

https://builds.apache.org/job/ZooKeeper_branch35_jdk8/52/

Also, the description indicates that the change here should be reverted once ZOOKEEPER-2136 is fixed.

CC [~phunt]

> Make testPortChange() less flaky
> --------------------------------
>
>                 Key: ZOOKEEPER-2137
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2137
>             Project: ZooKeeper
>          Issue Type: Sub-task
>            Reporter: Hongchao Deng
>            Assignee: Hongchao Deng
>             Fix For: 3.5.2, 3.6.0
>
>         Attachments: ZOOKEEPER-2137.patch
>
>
> The cause of flaky failure of testPortChange() is a race in sync().
> I figured out it could take some time to fix sync(). Meanwhile, we can make testPortChange() less flaky by doing reconfig on the leader. We can change this back in the fix of ZOOKEEPER-2136.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)