# Shards stuck in relocating

**URL:** <https://discuss.elastic.co/t/shards-stuck-in-relocating/41336>\
**Category:** Elasticsearch\
**Created:** [February 10, 2016, 12:50am UTC](https://discuss.elastic.co/t/shards-stuck-in-relocating/41336 "2016-02-10T00:50:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bwgriffith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bwgriffith/32/7695_2.png) [@bwgriffith](https://discuss.elastic.co/u/bwgriffith)\
**Post date:** [February 10, 2016, 12:50am UTC](https://discuss.elastic.co/t/shards-stuck-in-relocating/41336/1 "2016-02-10T00:50:01Z")

</div>

We had a cluster go into recovery today due to an outage. It has recovered, but there seems to be 2 shards stuck in relocation. The cluster is green, but search is extremely slow to non-responsive (Kibana times out). We have shut down indexing in the meantime.

-XGET '[http://localhost:9200/\_cluster/health?pretty](http://localhost:9200/_cluster/health?pretty)'

returns

{  
"cluster\_name" : "elasticsearch",  
"status" : "green",  
"timed\_out" : false,  
"number\_of\_nodes" : 5,  
"number\_of\_data\_nodes" : 5,  
"active\_primary\_shards" : 6161,  
"active\_shards" : 12322,  
"relocating\_shards" : 2,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 0,  
"delayed\_unassigned\_shards" : 0,  
"number\_of\_pending\_tasks" : 1684060,  
"number\_of\_in\_flight\_fetch" : 0,  
"task\_max\_waiting\_in\_queue\_millis" : 38878795,  
"active\_shards\_percent\_as\_number" : 100.0  
}

We are running ES 2.0

Where should we start troubleshooting?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [February 10, 2016, 12:38pm UTC](https://discuss.elastic.co/t/shards-stuck-in-relocating/41336/2 "2016-02-10T12:38:12Z")

</div>

Though it may or may not be directly related to the issues you are having, I would recommend you reconsider your indexing strategy, because that is a very large number of shards for a cluster that size.

---

<div class="post-metadata">

**Author:** ![bwgriffith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bwgriffith/32/7695_2.png) [@bwgriffith](https://discuss.elastic.co/u/bwgriffith)\
**Post date:** [February 10, 2016, 3:46pm UTC](https://discuss.elastic.co/t/shards-stuck-in-relocating/41336/3 "2016-02-10T15:46:38Z")

</div>

Yeah thanks, this is a proof of concept currently, so I've been using ES defaults (5shards/index), which has quickly blown up when combined with rolling daily indexes. Definitely need to address that issue.

In regards to this issue, I bounced the master node, and every re-distributed and ended up fixing itself.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:17pm UTC](https://discuss.elastic.co/t/shards-stuck-in-relocating/41336/4 "2017-07-05T23:17:33Z")

</div>