# Reset the IndexShardRoutingTable? **URL:** \ **Category:** Elasticsearch\ **Created:** [May 7, 2013, 7:33pm UTC](https://discuss.elastic.co/t/reset-the-indexshardroutingtable/11863 "2013-05-07T19:33:24Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Jerome\_Gagnon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jerome_gagnon/32/2178_2.png) [@Jerome\_Gagnon](https://discuss.elastic.co/u/Jerome_Gagnon)\ **Post date:** [May 7, 2013, 7:33pm UTC](https://discuss.elastic.co/t/reset-the-indexshardroutingtable/11863/1 "2013-05-07T19:33:24Z")
Heya everybody, Last night I had an index with many documents and without replicas that had disk failure resulting in 2 lost shards... This is bad, but we are currently in the process of reindexing and I just want my cluster to be back in green in the meantime. I read in another issue, that a dummy method is to create a similar index locally and move the shard to be recovered. However, I ran an reroute allocate command with "allow\_primary": 1 for those shards, so when I try to recover with the dummy method this is the outcome I get; [https://gist.github.com/jgagnon1/a4ebc27b17e8451af59e](https://gist.github.com/jgagnon1/a4ebc27b17e8451af59e) So my question, is there a way to reset the IndexShardRoutingTable (other than restarting the whole cluster) to remove the allow\_primary setting into those shards ? Many thanks Jerome -- 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:** ![Jerome\_Gagnon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jerome_gagnon/32/2178_2.png) [@Jerome\_Gagnon](https://discuss.elastic.co/u/Jerome_Gagnon)\ **Post date:** [May 7, 2013, 8:24pm UTC](https://discuss.elastic.co/t/reset-the-indexshardroutingtable/11863/2 "2013-05-07T20:24:24Z")
This was the issue I talked about, is it still doable ? [http://elasticsearch-users.115913.n3.nabble.com/Recovering-after-shard-failure-td4018776.html](http://elasticsearch-users.115913.n3.nabble.com/Recovering-after-shard-failure-td4018776.html) On Tuesday, May 7, 2013 3:33:24 PM UTC-4, Jérôme Gagnon wrote: > Heya everybody, > > Last night I had an index with many documents and without replicas that > had disk failure resulting in 2 lost shards... This is bad, but we are > currently in the process of reindexing and I just want my cluster to be > back in green in the meantime. I read in another issue, that a dummy method > is to create a similar index locally and move the shard to be recovered. > However, I ran an reroute allocate command with "allow\_primary": 1 for > those shards, so when I try to recover with the dummy method this is the > outcome I get; [gist:a4ebc27b17e8451af59e · GitHub](https://gist.github.com/jgagnon1/a4ebc27b17e8451af59e) > > So my question, is there a way to reset the IndexShardRoutingTable (other > than restarting the whole cluster) to remove the allow\_primary setting into > those shards ? > > Many thanks > > Jerome -- 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:37am UTC](https://discuss.elastic.co/t/reset-the-indexshardroutingtable/11863/3 "2017-07-06T02:37:50Z")
Closed on July 6, 2017, 2:37am UTC