# Shards get stuck in RELOCATING state **URL:** \ **Category:** Elasticsearch\ **Created:** [November 20, 2012, 6:35pm UTC](https://discuss.elastic.co/t/shards-get-stuck-in-relocating-state/9771 "2012-11-20T18:35:19Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![arta](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@arta](https://discuss.elastic.co/u/arta)\ **Post date:** [November 20, 2012, 6:35pm UTC](https://discuss.elastic.co/t/shards-get-stuck-in-relocating-state/9771/1 "2012-11-20T18:35:19Z")
Hi, I see two shards are stuck in RELOCATING state, for more than 18 hours as of now. curl localhost:9200/\_status shows something like this: "7" : [ { "routing" : { "state" : "RELOCATING", "primary" : false, "node" : "fyNmNb0yRnuVq-xHLFNU-Q", "relocating\_node" : "Gm7QcAG0Tom-kZFNfL-IGQ", "shard" : 7, "index" : "i42" }, and it does not change. I don't see any errors in logs. (indices.recovery log level is default) indexing and search seem working, but not sure for the shards under relocation. curl command such as curl -XPUT localhost:9200/\_cluster/settings -d '{"transient":{"cluster.routing.allocation.cluster\_concurrent\_rebalance" : 10}}' does not come back. (does not even timeout) What is the best way to make it proceed? Thanks for your help. ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [November 20, 2012, 7:29pm UTC](https://discuss.elastic.co/t/shards-get-stuck-in-relocating-state/9771/2 "2012-11-20T19:29:41Z")
Quick question: do you have enough disk space on all the nodes? -- Ivan On Tue, Nov 20, 2012 at 10:35 AM, arta [artasano@sbcglobal.net](mailto:artasano@sbcglobal.net) wrote: > Hi, > I see two shards are stuck in RELOCATING state, for more than 18 hours as > of > now. > curl localhost:9200/\_status shows something like this: > "7" : [ { > "routing" : { > "state" : "RELOCATING", > "primary" : false, > "node" : "fyNmNb0yRnuVq-xHLFNU-Q", > "relocating\_node" : "Gm7QcAG0Tom-kZFNfL-IGQ", > "shard" : 7, > "index" : "i42" > }, > > and it does not change. > > I don't see any errors in logs. > (indices.recovery log level is default) > > What is the best way to make it proceed? > > Thanks for your help. > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Shards-get-stuck-in-RELOCATING-state-tp4025778.html](http://elasticsearch-users.115913.n3.nabble.com/Shards-get-stuck-in-RELOCATING-state-tp4025778.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- -- ---
**Author:** ![arta](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@arta](https://discuss.elastic.co/u/arta)\ **Post date:** [November 20, 2012, 10:00pm UTC](https://discuss.elastic.co/t/shards-get-stuck-in-relocating-state/9771/3 "2012-11-20T22:00:49Z")
Thanks Ivan. Yes I have enough diskspace. ---
**Author:** ![arta](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@arta](https://discuss.elastic.co/u/arta)\ **Post date:** [November 20, 2012, 10:02pm UTC](https://discuss.elastic.co/t/shards-get-stuck-in-relocating-state/9771/4 "2012-11-20T22:02:02Z")
Additional notes: indexing and search seem working, but not sure for the shards under relocation. curl command such as curl -XPUT localhost:9200/\_cluster/settings -d '{"transient":{"cluster.routing.allocation.cluster\_concurrent\_rebalance" : 10}}' does not come back. (does not even timeout) ---
**Author:** ![Chris\_Male](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_male/32/2607_2.png) [@Chris\_Male](https://discuss.elastic.co/u/Chris_Male)\ **Post date:** [November 21, 2012, 9:31pm UTC](https://discuss.elastic.co/t/shards-get-stuck-in-relocating-state/9771/5 "2012-11-21T21:31:13Z")
Hi, Are you able to give us some information about what version of Elasticsearch you're using and any information about your cluster layout / network layout. On Wednesday, November 21, 2012 11:02:05 AM UTC+13, arta wrote: > Additional notes: > > indexing and search seem working, but not sure for the shards under > relocation. > curl command such as > curl -XPUT localhost:9200/\_cluster/settings -d > '{"transient":{"cluster.routing.allocation.cluster\_concurrent\_rebalance" : > 10}}' > does not come back. (does not even timeout) > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Shards-get-stuck-in-RELOCATING-state-tp4025778p4025783.html](http://elasticsearch-users.115913.n3.nabble.com/Shards-get-stuck-in-RELOCATING-state-tp4025778p4025783.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). -- ---
**Author:** ![arta](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@arta](https://discuss.elastic.co/u/arta)\ **Post date:** [November 22, 2012, 12:14am UTC](https://discuss.elastic.co/t/shards-get-stuck-in-relocating-state/9771/6 "2012-11-22T00:14:33Z")
Hi Chris, thanks for the reply. I'm using 0.19.3. I have 19 data nodes in one cluster, all are master eligible, they are in our private network. Is this enough info for you? ---
**Author:** ![Thomas\_Peuss](https://avatars.discourse-cdn.com/v4/letter/t/22d042/32.png) [@Thomas\_Peuss](https://discuss.elastic.co/u/Thomas_Peuss)\ **Post date:** [November 23, 2012, 1:32pm UTC](https://discuss.elastic.co/t/shards-get-stuck-in-relocating-state/9771/7 "2012-11-23T13:32:18Z")
Hi! Am Donnerstag, 22. November 2012 01:14:37 UTC+1 schrieb arta: > Hi Chris, thanks for the reply. > > I'm using 0.19.3. > I have 19 data nodes in one cluster, all are master eligible, they are in > our private network. > Is this enough info for you? We are running an 8 node cluster and I must say that it was not very stable before we installed 0.19.11 (we jumped from 0.19.4). Now we are running 0.19.11 and it is rock solid. We had similar problems with stuck shards. CU Thomas -- ---
**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, 3:03am UTC](https://discuss.elastic.co/t/shards-get-stuck-in-relocating-state/9771/8 "2017-07-06T03:03:09Z")