Details
-
Sub-task
-
Status: Reopened
-
Major
-
Resolution: Unresolved
-
3.6.0
-
None
-
None
Description
The unit test added in ZOOKEEPER-3109 turns out to be quite flaky.
See https://builds.apache.org/job/zOOkeeper-Find-Flaky-Tests/511/artifact/report.html
Recent failure builds:
https://builds.apache.org/job/ZooKeeper-trunk//181
https://builds.apache.org/job/ZooKeeper-trunk//179
Snapshot of the failure:
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter_stillHasMajority Error Message Server 0 should have joined quorum by now Stacktrace junit.framework.AssertionFailedError: Server 0 should have joined quorum by now at org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElection(QuorumPeerMainTest.java:1482) at org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter_stillHasMajority(QuorumPeerMainTest.java:1431) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
Attachments
Issue Links
- is caused by
-
ZOOKEEPER-3109 Avoid long unavailable time due to voter changed mind when activating the leader during election
- Resolved
- is duplicated by
-
ZOOKEEPER-3214 Flaky test: org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter
- Resolved