[
https://issues.apache.org/jira/browse/ZOOKEEPER-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13929866#comment-13929866
]
Helen Hastings commented on ZOOKEEPER-1870:
-------------------------------------------
Thanks Michi. However, I also see this error happen every once in a while when
the test succeeds. I believe the reason it happens more often when the test
fails is because over 50 seconds are spent trying to get servers 1 and 2 to
connect (we get all the way to here):
2014-02-28 02:30:39,673 [myid:2] - INFO
[QuorumPeer[myid=2]/127.0.0.1:11227:FastLeaderElection@846] - Notification time
out: 51200
so there is just more time/opportunity for the error to happen, as opposed to
the success case when the servers are able to connect within a second or faster.
This could still be related even though it happens in both the success and
failure case. Either way I'll continue looking into it on my own as well.
> flakey test in StandaloneDisabledTest.startSingleServerTest
> -----------------------------------------------------------
>
> Key: ZOOKEEPER-1870
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1870
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Affects Versions: 3.5.0
> Reporter: Patrick Hunt
> Assignee: Michi Mutsuzaki
> Priority: Critical
>
> I'm seeing lots of the following failure. Seems like a flakey test (passes
> every so often).
> {noformat}
> junit.framework.AssertionFailedError: client could not connect to
> reestablished quorum: giving up after 30+ seconds.
> at
> org.apache.zookeeper.test.ReconfigTest.testNormalOperation(ReconfigTest.java:143)
> at
> org.apache.zookeeper.server.quorum.StandaloneDisabledTest.startSingleServerTest(StandaloneDisabledTest.java:75)
> at
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
