-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Fix Broken Index Shard Snapshot File Preventing Snapshot Creation #41476
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
Conversation
…astic#41310) * The problem here is that if we run into a corrupted index-N file, instead of generating a new index-(N+1) file, we instead set the newest index generation to -1 and thus tried to create `index-0` * If `index-0` is corrupt, this prevents us from ever creating a new snapshot using the broken shard, because we are unable to create `index-0` since it already exists * Fixed by still using the index generation for naming the next index file, even if it was a broken index file * Added test that makes sure restoring as well as snapshotting on top of the broken shard index file work as expected * closes elastic#41304
Pinging @elastic/es-distributed |
Jenkins run elasticsearch-ci/1 |
12 similar comments
Jenkins run elasticsearch-ci/1 |
Jenkins run elasticsearch-ci/1 |
Jenkins run elasticsearch-ci/1 |
Jenkins run elasticsearch-ci/1 |
Jenkins run elasticsearch-ci/1 |
Jenkins run elasticsearch-ci/1 |
Jenkins run elasticsearch-ci/1 |
Jenkins run elasticsearch-ci/1 |
Jenkins run elasticsearch-ci/1 |
Jenkins run elasticsearch-ci/1 |
Jenkins run elasticsearch-ci/1 |
Jenkins run elasticsearch-ci/1 |
index-0
index-0
is corrupt, this prevents us from ever creating a new snapshot using the broken shard, because we are unable to createindex-0
since it already existsbackport of #41310