[ZOOKEEPER-3023] Flaky test: org.apache.zookeeper.server.quorum.Zab1_0Test.testNormalFollowerRunWithDiff

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.6.0
• Labels: pull-request-available
• Assignee: Kezhu Wang
• Reporter: Pravin Dsilva
• Created: 20/Apr/18 12:59
• Updated: 19/Sep/24 06:29
• Resolved: 19/Sep/24 06:29

Description

Getting the following error on master branch:

Error Message

expected:<4294967298> but was:<0>

Stacktrace

junit.framework.AssertionFailedError: expected:<4294967298> but was:<0> at org.apache.zookeeper.server.quorum.Zab1_0Test$5.converseWithFollower(Zab1_0Test.java:876) at org.apache.zookeeper.server.quorum.Zab1_0Test.testFollowerConversation(Zab1_0Test.java:523) at org.apache.zookeeper.server.quorum.Zab1_0Test.testNormalFollowerRunWithDiff(Zab1_0Test.java:791) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

Flaky test:https://builds.apache.org/job/ZooKeeper-trunk-java10/141/testReport/junit/org.apache.zookeeper.server.quorum/Zab1_0Test/testNormalFollowerRunWithDiff/

Issue Links

• is caused by: ZOOKEEPER-3911 Data inconsistency caused by DIFF sync uncommitted log
• is caused by: ZOOKEEPER-2678 Large databases take a long time to regain a quorum
• is related to: ZOOKEEPER-4643 Committed txns may be improperly truncated if follower crashes right after updating currentEpoch but before persisting txns to disk
• is related to: ZOOKEEPER-4646 Committed txns may still be lost if followers crash after replying ACK of NEWLEADER but before writing txns to disk
• is superceded by: ZOOKEEPER-4785 Txn loss due to race condition in Learner.syncWithLeader() during DIFF sync
• is superceded by: ZOOKEEPER-4394 Learner.syncWithLeader got NullPointerException
• relates to: ZOOKEEPER-4646 Committed txns may still be lost if followers crash after replying ACK of NEWLEADER but before writing txns to disk
• links to: GitHub Pull Request #1848