[
https://issues.apache.org/jira/browse/ZOOKEEPER-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Han updated ZOOKEEPER-2152:
-----------------------------------
Attachment: ZOOKEEPER-2152.patch
First stab on the patch attempts to fix the root cause I mentioned. I
introduced a specific flag that only applicable in the context of reconfig test
and the purpose of that flag is to teach ZK client so it would not try cycling
through the server during reconnection attempt, otherwise the cycling inside ZK
client would interfere with the cycling logic in our test case. Since the flag
is only applicable for testing there is no API attached to it.
My endurance tests (10k+ runs of ReconfigTest) on both mac and Ubuntu indicates
that this fixes all the previous failures described in this JIRA and the
comments.
> Intermittent failure in TestReconfig.cc
> ---------------------------------------
>
> Key: ZOOKEEPER-2152
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2152
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: c client
> Reporter: Michi Mutsuzaki
> Assignee: Michael Han
> Labels: reconfiguration
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2152.patch
>
>
> I'm seeing this failure in the c client test once in a while:
> {noformat}
> [exec]
> /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/c/tests/TestReconfig.cc:474:
> Assertion: assertion failed [Expression: found != string::npos,
> 10.10.10.4:2004 not in newComing list]
> {noformat}
> https://builds.apache.org/job/ZooKeeper-trunk/2640/console
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
