Skip to content

Fix CoordinatorTests.testUnresponsiveLeaderDetectedEventually #64462

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

Merged
Changes from all 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
Original file line number Diff line number Diff line change
Expand Up @@ -539,6 +539,14 @@ public void testUnresponsiveLeaderDetectedEventually() {
+ defaultMillis(PUBLISH_TIMEOUT_SETTING)
// there might be a term bump causing another election
+ DEFAULT_ELECTION_DELAY
// in clusters with 5 nodes the chances of concurrent elections
// increase, meaning that it takes longer to get a leader elected
// so we should take into account those cases to ensure that the
// cluster stabilises over time. See #63918 for a really messy scenario.
+ DEFAULT_ELECTION_DELAY
// additionally take into account that publications might take longer
// until the new leader detects that the old leader is unresponsive
+ defaultMillis(PUBLISH_TIMEOUT_SETTING)

// then wait for both of:
+ Math.max(
Expand Down