# Expluge delete can cause the shard to reinitialize **URL:** \ **Category:** Elasticsearch\ **Created:** [July 8, 2013, 4:06am UTC](https://discuss.elastic.co/t/expluge-delete-can-cause-the-shard-to-reinitialize/12689 "2013-07-08T04:06:19Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ywtsang](https://avatars.discourse-cdn.com/v4/letter/y/a698b9/32.png) [@ywtsang](https://discuss.elastic.co/u/ywtsang)\ **Post date:** [July 8, 2013, 4:06am UTC](https://discuss.elastic.co/t/expluge-delete-can-cause-the-shard-to-reinitialize/12689/1 "2013-07-08T04:06:19Z")
es version: 0.90.1 actions: 1. delete more than half of documents from the index 2. flush 3. call "/\_optimize?only\_expunge\_deletes=true" observe: 1. over half of the index spaces are released 2. 1 of the shards is marked as "initializing" (i.e. yellow in elasticsearch head), it is not "relocating/purple" and the cluster state is turned to yellow 3. after the shard is initialized, the cluster become green and another shard is doing relocating (purple) so my question is expunging the index to release disk spaces can trigger the index to reinitialize/relocating the shards? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:27am UTC](https://discuss.elastic.co/t/expluge-delete-can-cause-the-shard-to-reinitialize/12689/2 "2017-07-06T02:27:46Z")
Closed on July 6, 2017, 2:27am UTC