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

bleskes · 2013-09-25T15:02:58Z

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.

…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

…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

bleskes closed this as completed in 1644444 Sep 25, 2013

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

bleskes commented Sep 25, 2013

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

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

Comments

bleskes commented Sep 25, 2013