-
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] SnapshotsStressTestsIT failure #101029
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
DaveCTurner
added
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
labels
Oct 18, 2023
elasticsearchmachine
added
blocker
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
labels
Oct 18, 2023
Pinging @elastic/es-distributed (Team:Distributed) |
volodk85
added
low-risk
An open issue or test failure that is a low risk to future releases
and removed
blocker
labels
Oct 20, 2023
DaveCTurner
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 24, 2023
This was referenced Oct 25, 2023
I've found a way to reproduce this - it requires deleting an index during out-of-order snapshot finalization, so it's pretty delicate. |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Jan 2, 2024
Today if an index is deleted during a very specific order of snapshot finalizations then it's possible we'll miscalculate the latest shard generations for the shards in that index, causing the deletion of a shard-level `index-UUID` blob which prevents further snapshots of that shard. Closes elastic#101029
One more at elasticsearch / periodic / platform-support / main / debian-11 / platform-support-unix
|
elasticsearchmachine
pushed a commit
that referenced
this issue
Jan 15, 2024
Today if an index is deleted during a very specific order of snapshot finalizations then it's possible we'll miscalculate the latest shard generations for the shards in that index, causing the deletion of a shard-level `index-UUID` blob which prevents further snapshots of that shard. Closes #101029
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Jan 15, 2024
Today if an index is deleted during a very specific order of snapshot finalizations then it's possible we'll miscalculate the latest shard generations for the shards in that index, causing the deletion of a shard-level `index-UUID` blob which prevents further snapshots of that shard. Backports elastic#103817 to 8.12 Closes elastic#101029
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Jan 15, 2024
Today if an index is deleted during a very specific order of snapshot finalizations then it's possible we'll miscalculate the latest shard generations for the shards in that index, causing the deletion of a shard-level `index-UUID` blob which prevents further snapshots of that shard. Backports elastic#103817 to 7.17 Closes elastic#101029
elasticsearchmachine
pushed a commit
that referenced
this issue
Jan 15, 2024
Today if an index is deleted during a very specific order of snapshot finalizations then it's possible we'll miscalculate the latest shard generations for the shards in that index, causing the deletion of a shard-level `index-UUID` blob which prevents further snapshots of that shard. Backports #103817 to 8.12 Closes #101029
elasticsearchmachine
pushed a commit
that referenced
this issue
Jan 18, 2024
* Fix deleting index during snapshot finalization Today if an index is deleted during a very specific order of snapshot finalizations then it's possible we'll miscalculate the latest shard generations for the shards in that index, causing the deletion of a shard-level `index-UUID` blob which prevents further snapshots of that shard. Backports #103817 to 7.17 Closes #101029 * Test fixup
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
CI Link
https://gradle-enterprise.elastic.co/s/q7czw7twlsxik
Repro line
':server:internalClusterTest' --tests "org.elasticsearch.snapshots.SnapshotStressTestsIT.testRandomActivities" -Dtests.seed=F1980E360247D5B1 -Dtests.locale=ar-LY -Dtests.timezone=Chile/Continental -Druntime.java=21
Does it reproduce?
No
Applicable branches
main
Failure history
No response
Failure excerpt
This failure is super super rare, I've seen it maybe twice after running this test in a loop for several days. It indicates we're doing something wrong with shard generations still.
The text was updated successfully, but these errors were encountered: