[
https://issues.apache.org/jira/browse/ZOOKEEPER-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311604#comment-15311604
]
Alexander Shraer commented on ZOOKEEPER-2152:
---------------------------------------------
Hi Michael,
Thanks again for investigating this and producing the patch!
As I mentioned I'm not really familiar with C client reconfig, but I'd still
like to understand your findings better. Could you please
explain again, I'm not sure I completely got it. Here are my questions:
1) AFAIU the state of the servers shouldn't matter for this test, as this is
the client-side library.
2) I assumed each client has independent state from other clients, but you're
indicating that this isn't true. Why is that ? Are multiple
clients sharing the same state ?
3) Does the Java client library have the same issue ? The C test should be more
or less a copy of the Java one. Or why isn't the state sharing happening there ?
Thanks,
Alex
> 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)
