-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[CI] ConcurrentSnapshotsIT testMasterFailoverOnFinalizationLoop failing #101876
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
medium-risk
An open issue or test failure that is a medium risk to future releases
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
>test-failure
Triaged test failures from CI
Comments
tlrx
added
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
labels
Nov 7, 2023
elasticsearchmachine
added
blocker
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
labels
Nov 7, 2023
Pinging @elastic/es-distributed (Team:Distributed) |
volodk85
added
medium-risk
An open issue or test failure that is a medium risk to future releases
and removed
blocker
labels
Nov 7, 2023
This failed this morning and test history shows four failures in the last week. According to test-triage rules we should mute a test that fails more than once, so I made the mute PR at #102404 |
aniljangirdev
pushed a commit
to aniljangirdev/elasticsearch
that referenced
this issue
Nov 21, 2023
This failed four times in the last week. The issue to fix is elastic#101876
elasticsearchmachine
pushed a commit
that referenced
this issue
Nov 27, 2023
Snapshot listeners can be concurrently resolved from two different *clusterApplierService* and *masterService* task threads. If a listener is a **single action** listener, meaning that it has to be resolved only once, the following traces can occur, see #101876 ``` at org.elasticsearch.action.ActionListener$4.assertFirstRun(ActionListener.java:324) at org.elasticsearch.action.ActionListener$4.onFailure(ActionListener.java:335) ``` Fix Line up *resolve listener and remove it from tracking collection* operations over snapshot listeners in order to avoid double invocation by separate threads Fix for #101876
timgrein
pushed a commit
to timgrein/elasticsearch
that referenced
this issue
Nov 30, 2023
…102439) Snapshot listeners can be concurrently resolved from two different *clusterApplierService* and *masterService* task threads. If a listener is a **single action** listener, meaning that it has to be resolved only once, the following traces can occur, see elastic#101876 ``` at org.elasticsearch.action.ActionListener$4.assertFirstRun(ActionListener.java:324) at org.elasticsearch.action.ActionListener$4.onFailure(ActionListener.java:335) ``` Fix Line up *resolve listener and remove it from tracking collection* operations over snapshot listeners in order to avoid double invocation by separate threads Fix for elastic#101876
2lambda123
pushed a commit
to 2lambda123/elastic-elasticsearch
that referenced
this issue
May 3, 2024
This failed four times in the last week. The issue to fix is elastic/elasticsearch#101876
2lambda123
pushed a commit
to 2lambda123/elastic-elasticsearch
that referenced
this issue
May 3, 2024
This failed four times in the last week. The issue to fix is elastic/elasticsearch#101876
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
medium-risk
An open issue or test failure that is a medium risk to future releases
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
>test-failure
Triaged test failures from CI
This test failed two times today with a listener being executed twice:
A similar test failure was reported in #101652 and fixed by #99355, but because the stacktrace is different I report it in a new issue.
https://gradle-enterprise.elastic.co/s/taabgxondrawu/
https://gradle-enterprise.elastic.co/s/vs5aky72bagkk/
Build scan:
https://gradle-enterprise.elastic.co/s/vs5aky72bagkk/tests/:server:internalClusterTest/org.elasticsearch.snapshots.ConcurrentSnapshotsIT/testMasterFailoverOnFinalizationLoop
Reproduction line:
Applicable branches:
main, 8.11
Reproduces locally?:
Didn't try
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.snapshots.ConcurrentSnapshotsIT&tests.test=testMasterFailoverOnFinalizationLoop
Failure excerpt:
The text was updated successfully, but these errors were encountered: