-
Notifications
You must be signed in to change notification settings - Fork 25k
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] SnapshotStressTestsIT testRandomActivities failing #101028
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
ywangd
added
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
low-risk
An open issue or test failure that is a low risk to future releases
labels
Oct 18, 2023
elasticsearchmachine
added
the
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
label
Oct 18, 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
low-risk
An open issue or test failure that is a low risk to future releases
labels
Oct 23, 2023
ywangd
added a commit
to ywangd/elasticsearch
that referenced
this issue
Oct 29, 2023
When a snapshot is completed as a SnapshotsInProgress entry in cluster state and also queued for next operations, it can lead to double finalization of the snapshot if the entry in cluster state is processed first. This PR fixes it by only start finalization if it is *not* already in endingSnapshots. The PR also adds a specific test case for the double finalization issue (manifested as NPE). Resolves: elastic#101028
ywangd
added a commit
that referenced
this issue
Oct 30, 2023
When a snapshot is completed as a SnapshotsInProgress entry in cluster state and also queued for next operations, it can lead to double finalization of the snapshot if the entry in cluster state is processed first. This PR fixes it by only start finalization if it is *not* already in endingSnapshots. The PR also adds a specific test case for the double finalization issue (manifested as NPE). Resolves: #101028
ywangd
added a commit
to ywangd/elasticsearch
that referenced
this issue
Oct 30, 2023
When a snapshot is completed as a SnapshotsInProgress entry in cluster state and also queued for next operations, it can lead to double finalization of the snapshot if the entry in cluster state is processed first. This PR fixes it by only start finalization if it is *not* already in endingSnapshots. The PR also adds a specific test case for the double finalization issue (manifested as NPE). Resolves: elastic#101028
elasticsearchmachine
pushed a commit
that referenced
this issue
Oct 30, 2023
When a snapshot is completed as a SnapshotsInProgress entry in cluster state and also queued for next operations, it can lead to double finalization of the snapshot if the entry in cluster state is processed first. This PR fixes it by only start finalization if it is *not* already in endingSnapshots. The PR also adds a specific test case for the double finalization issue (manifested as NPE). Resolves: #101028
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 NPE issue is different from #99477 and #99516
CI Link
https://gradle-enterprise.elastic.co/s/v7icocftg32uc/tests/task/:server:internalClusterTest/details/org.elasticsearch.snapshots.SnapshotStressTestsIT/testRandomActivities%20%7Bseed=%5B32DA52B8E1546052:7737AEA21D8C5249%5D%7D?top-execution=1
Repro line
./gradlew ':server:internalClusterTest' --tests "org.elasticsearch.snapshots.SnapshotStressTestsIT.testRandomActivities {seed=[32DA52B8E1546052:7737AEA21D8C5249]}" -Dtests.seed=32DA52B8E1546052 -Dtests.locale=cs -Dtests.timezone=America/El_Salvador -Druntime.java=21
Does it reproduce?
No
Applicable branches
main
Failure history
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.snapshots.SnapshotStressTestsIT&tests.test=testRandomActivities%20%7Bseed%3D%5B32DA52B8E1546052:7737AEA21D8C5249%5D%7D
Failure excerpt
The text was updated successfully, but these errors were encountered: