Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Raft scenarios with dependency on dispatch order #6748

Merged
merged 4 commits into from
Jan 9, 2025
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions tests/raft_scenarios/reconfig_01_23
Original file line number Diff line number Diff line change
Expand Up @@ -42,13 +42,14 @@ assert_commit_idx,0,8
assert_detail,0,leadership_state,None
assert_detail,0,retirement_phase,RetiredCommitted

# 2 becomes leader
assert_detail,2,leadership_state,Leader
# One of the continuing nodes has become leader
emit_signature,3
periodic_all,10
dispatch_all
periodic_all,10
dispatch_all
assert_commit_idx,2,9
assert_commit_idx,3,9

# 0 becomes a follower again, because it receives messages
# from 2 before 2 realises 0 is retired committed.
Expand All @@ -65,5 +66,7 @@ replicate,3,some_tx
emit_signature,3
periodic_all,10
dispatch_all
periodic_all,10
dispatch_all
assert_commit_idx,2,11
assert_commit_idx,2,11
assert_commit_idx,3,11
4 changes: 3 additions & 1 deletion tests/raft_scenarios/reconfig_01_el0_23
Original file line number Diff line number Diff line change
Expand Up @@ -91,5 +91,7 @@ replicate,5,some_tx
emit_signature,5
periodic_all,10
dispatch_all
periodic_all,10
dispatch_all
assert_commit_idx,2,13
assert_commit_idx,2,13
assert_commit_idx,3,13
Loading