# Shards stuck in recovery for long periods **URL:** \ **Category:** Elasticsearch\ **Created:** [September 3, 2013, 11:45pm UTC](https://discuss.elastic.co/t/shards-stuck-in-recovery-for-long-periods/13450 "2013-09-03T23:45:33Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![robert\_3](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robert_3/32/2132_2.png) [@robert\_3](https://discuss.elastic.co/u/robert_3)\ **Post date:** [September 3, 2013, 11:45pm UTC](https://discuss.elastic.co/t/shards-stuck-in-recovery-for-long-periods/13450/1 "2013-09-03T23:45:33Z")
Hi all, Seeing some recent problems on master where shortly after a cluster reboot and full recovery (all shards green, all nodes connected), on occasion a shard or two will start being marked as recovery (rebalancing is disabled, so it's not due to it being moved around). After a few minutes they sometimes say they're initializing (an order of magnitude after the amount of time it should take to transfer the shard given all the throttling settings and network), but in the end they'll never come back up and just remain in that state until I manually reroute the shard or restart the server. We were seeing similar problems on a larger scale on 0.90.3 (multiple shards never recovering, all of them replicas of the same primary). I thought I saw something about that being fixed on github, but can't recall the exact issue now. Any chance these are related? Is there something I can do to debug what is going on while the shards say initializing/recovering? Nothing is currently coming up in my logs. ## Thanks, Robert Deaton -- 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:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [September 12, 2013, 10:12am UTC](https://discuss.elastic.co/t/shards-stuck-in-recovery-for-long-periods/13450/2 "2013-09-12T10:12:09Z")
Hey, anything in the logs, cluster state, hot\_threads output, which might add some information to this? I am worried about the 'on occasion' part. If everything is good and you do not change the amount of nodes in your cluster, there should be no need to mark a shard to recover, so something has happened at that stage. Anything in the logs then? --Alex On Wed, Sep 4, 2013 at 1:45 AM, Robert Deaton [robert@quizlet.com](mailto:robert@quizlet.com) wrote: > Hi all, > > Seeing some recent problems on master where shortly after a cluster reboot > and full recovery (all shards green, all nodes connected), on occasion a > shard or two will start being marked as recovery (rebalancing is disabled, > so it's not due to it being moved around). After a few minutes they > sometimes say they're initializing (an order of magnitude after the amount > of time it should take to transfer the shard given all the throttling > settings and network), but in the end they'll never come back up and just > remain in that state until I manually reroute the shard or restart the > server. > > We were seeing similar problems on a larger scale on 0.90.3 (multiple > shards never recovering, all of them replicas of the same primary). I > thought I saw something about that being fixed on github, but can't recall > the exact issue now. Any chance these are related? Is there something I can > do to debug what is going on while the shards say initializing/recovering? > Nothing is currently coming up in my logs. > > ## Thanks, > > Robert Deaton > > -- > 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). -- 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:16am UTC](https://discuss.elastic.co/t/shards-stuck-in-recovery-for-long-periods/13450/3 "2017-07-06T02:16:55Z")