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

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
Closed

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

bleskes opened this issue Sep 26, 2013 · 0 comments
Assignees
@bleskes
Labels
>bug v0.90.6 v1.0.0.Beta1

Comments

@bleskes
Copy link
Contributor

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
@bleskes
Add indexUUID to mapping-updated and mapping-refresh events and make …
6224570 
…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 mentioned this issue Sep 26, 2013
Closed
bleskes added a commit that referenced this issue Sep 27, 2013
@bleskes
Add indexUUID to mapping-updated and mapping-refresh events and make …
0618fa6 
…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
@bleskes
Add indexUUID to mapping-updated and mapping-refresh events and make …
764daae 
…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
Assignees

@bleskes bleskes

Labels
>bug v0.90.6 v1.0.0.Beta1
Projects
None yet
Milestone
No milestone
1 participant
@bleskes