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.

Sign up for GitHub

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

Jump to bottom

[CI] CoordinatorTests testElectionSchedulingAfterDiscoveryOutage failing #111155

Closed
elasticsearchmachine opened this issue Jul 22, 2024 · 2 comments · Fixed by #111629
Closed

[CI] CoordinatorTests testElectionSchedulingAfterDiscoveryOutage failing #111155

elasticsearchmachine opened this issue Jul 22, 2024 · 2 comments · Fixed by #111629
Assignees
@DaveCTurner
Labels
:Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Meta label for distributed team (obsolete) >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":server:test" --tests "org.elasticsearch.cluster.coordination.CoordinatorTests.testElectionSchedulingAfterDiscoveryOutage" -Dtests.seed=DC077D013F80A90B -Dtests.locale=sr-CS -Dtests.timezone=Africa/Harare -Druntime.java=22

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: node2 has applied its state 
Expected: <19L>
     but: was <18L>

Issue Reasons:

  • [main] 2 failures in test testElectionSchedulingAfterDiscoveryOutage (0.2% fail rate in 892 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-platform-support (12.5% fail rate in 16 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. >test-failure Triaged test failures from CI Team:Distributed Meta label for distributed team (obsolete) needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jul 22, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-distributed (Team:Distributed)

@pxsalehi pxsalehi self-assigned this Jul 26, 2024
@pxsalehi pxsalehi added medium-risk An open issue or test failure that is a medium risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jul 29, 2024
@DaveCTurner DaveCTurner assigned DaveCTurner and unassigned pxsalehi Aug 6, 2024
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this issue Aug 6, 2024
@DaveCTurner
Fix testElectionSchedulingAfterDiscoveryOutage
676f955 
We need to wait a little longer to deal with the case that closing the
`PeerFinder` on the master triggers a disconnect, removing the third
node from the cluster, and requiring another round of discovery to
recover.

Closes elastic#111155
@DaveCTurner DaveCTurner mentioned this issue Aug 6, 2024
Merged
@DaveCTurner DaveCTurner added low-risk An open issue or test failure that is a low risk to future releases and removed medium-risk An open issue or test failure that is a medium risk to future releases labels Aug 6, 2024
@DaveCTurner
Copy link
Contributor

Just a test bug, downgrading to low-risk.

DaveCTurner added a commit that referenced this issue Aug 6, 2024
@DaveCTurner
Fix testElectionSchedulingAfterDiscoveryOutage (#111629)
4a6bcd8 
We need to wait a little longer to deal with the case that closing the
`PeerFinder` on the master triggers a disconnect, removing the third
node from the cluster, and requiring another round of discovery to
recover.

Closes #111155
mhl-b pushed a commit that referenced this issue Aug 8, 2024
@DaveCTurner @mhl-b
Fix testElectionSchedulingAfterDiscoveryOutage (#111629)
4a3cbac 
We need to wait a little longer to deal with the case that closing the
`PeerFinder` on the master triggers a disconnect, removing the third
node from the cluster, and requiring another round of discovery to
recover.

Closes #111155
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Sep 4, 2024
@DaveCTurner @cbuescher
Fix testElectionSchedulingAfterDiscoveryOutage (elastic#111629)
1a43e90 
We need to wait a little longer to deal with the case that closing the
`PeerFinder` on the master triggers a disconnect, removing the third
node from the cluster, and requiring another round of discovery to
recover.

Closes elastic#111155
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DaveCTurner DaveCTurner

Labels
:Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Meta label for distributed team (obsolete) >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix testElectionSchedulingAfterDiscoveryOutage DaveCTurner/elasticsearch
3 participants
@pxsalehi @DaveCTurner @elasticsearchmachine