There are settings you can change, see http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-indices.html#recovery
On 5 January 2015 at 12:50, Salman <[email protected]> wrote: > On ES 1.4.2 cluster, post cluster restart, 90% of shards are unassigned. Is > there a way to stop the whole cluster again, and force quicker reassignment > of shards. I researched and few users have had similiar issues, so am > hoping > someone can guide me on optimal way to fix this. > > > > > > -- > View this message in context: > http://elasticsearch-users.115913.n3.nabble.com/Large-Number-of-Shards-are-unassigned-post-cluster-restart-tp4068453.html > Sent from the ElasticSearch Users mailing list archive at Nabble.com. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/1420422652801-4068453.post%40n3.nabble.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9EZnvew-Bc%2BnKxZo%2B6fzeiYs%2BdsK0Q5epF1BJ5TeeFHA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
