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

Ensure we can recover cleanly into a leftover shard directory from a different index #10677

Closed
s1monw opened this issue Apr 20, 2015 · 0 comments
Closed

Ensure we can recover cleanly into a leftover shard directory from a different index #10677

s1monw opened this issue Apr 20, 2015 · 0 comments
Assignees
@s1monw
Labels
blocker :Distributed/Recovery Anything around constructing a new shard, either from a local or a remote source. >enhancement v2.0.0-beta1

Comments

@s1monw
Copy link
Contributor

s1monw commented Apr 20, 2015

this is a followup issue for #10461 where we now throw an exception if we try to allocate a shard where there already exists such a shards with a non-matching index UUID. This is an edge case but we should be able to recover cleanly in such a case an remove that leftover shard directory.
@s1monw s1monw self-assigned this Apr 20, 2015
@s1monw s1monw mentioned this issue Apr 20, 2015
Merged
@clintongormley clintongormley added :Distributed/Recovery Anything around constructing a new shard, either from a local or a remote source. >enhancement labels Jun 8, 2015
@s1monw s1monw mentioned this issue Jun 30, 2015
Closed
s1monw added a commit to s1monw/elasticsearch that referenced this issue Jul 1, 2015
@s1monw
Allow shards to be allocated if leftover shard from different index e…
5dc5fd5 
…xists.

If an index name is reused but a leftover shard still exists on any node
we fail repeatedly to allocate the shard since we now check the index UUID
before reusing data. This commit allows to recover even if there is such a
leftover shard by trying to archive the shard into a seperate directory.

Closes elastic#10677
@s1monw s1monw mentioned this issue Jul 14, 2015
Merged
s1monw added a commit to s1monw/elasticsearch that referenced this issue Jul 15, 2015
@s1monw
Allow shards to be allocated if leftover shard from different index e…
cdcfcf4 
…xists.

If an index name is reused but a leftover shard still exists on any node
we fail repeatedly to allocate the shard since we now check the index UUID
before reusing data. This commit allows to recover even if there is such a
leftover shard by deleting the leftover shard.

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

@s1monw s1monw

Labels
blocker :Distributed/Recovery Anything around constructing a new shard, either from a local or a remote source. >enhancement v2.0.0-beta1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@clintongormley @s1monw