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

Use the new index UUID to ensure mapping update events from older indices are not applied to new indices with the same name #3783

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

Comments

Projects
None yet
1 participant
@bleskes
Copy link
Member

bleskes commented Sep 26, 2013

This can currently happen if an index is repeatedly created by an indexing operation and deleted quickly afterwards.

@ghost ghost assigned bleskes Sep 26, 2013

bleskes added a commit to bleskes/elasticsearch that referenced this issue Sep 26, 2013

Add indexUUID to mapping-updated and mapping-refresh events and make …
…sure they are applied to an index with same UUID.

This can go wrong if indices with the same name are repeatably created and deleted.

Also - some minor clean up in ShardStateAction where shard started events could be added twice to the to-be-applied list where the second instance will be ignored.

Closes elastic#3783

@bleskes bleskes closed this in 1d7e20b Sep 27, 2013

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

Add indexUUID to mapping-updated and mapping-refresh events and make …
…sure they are applied to an index with same UUID.

This can go wrong if indices with the same name are repeatably created and deleted.

UUIDs can not be null anymore. If UUID is not available `_na_` will be used as a value.

Also - some minor clean up in ShardStateAction where shard started events could be added twice to the to-be-applied list where the second instance will be ignored.

Closes #3783

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

Add indexUUID to mapping-updated and mapping-refresh events and make …
…sure they are applied to an index with same UUID.

This can go wrong if indices with the same name are repeatably created and deleted.

UUIDs can not be null anymore. If UUID is not available `_na_` will be used as a value.

Also - some minor clean up in ShardStateAction where shard started events could be added twice to the to-be-applied list where the second instance will be ignored.

Closes elastic#3783
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.