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.

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

Quickly deleting and creating an index with the same name could cause errors due to lingering shard state change events #3778

Closed
bleskes opened this Issue Sep 25, 2013 · 0 comments

Comments

Projects
None yet
1 participant
@bleskes
Copy link
Member

bleskes commented Sep 25, 2013

In some rare occasions shard started/failed events from the previous index that still needed to be processed will be applied to the new index routing table.

bleskes added a commit that referenced this issue Sep 25, 2013

Introduced an index UUID which is added to the index's settings upon …
…creation. Used that UUID to verify old and delayed shard started/failed events are not applied to newer indexes with the same name.

Also, exceptions while processing batched events do not stop the rest of the events from being processed.

Closes #3778

@bleskes bleskes closed this in 1644444 Sep 25, 2013

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

Introduced an index UUID which is added to the index's settings upon …
…creation. Used that UUID to verify old and delayed shard started/failed events are not applied to newer indexes with the same name.

Also, exceptions while processing batched events do not stop the rest of the events from being processed.

Closes elastic#3778
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.