# Decomissioning node question, does not start moving shards
**URL:** https://discuss.elastic.co/t/decomissioning-node-question-does-not-start-moving-shards/94624
**Category:** Elasticsearch
**Created:** [July 26, 2017, 11:11am UTC](https://discuss.elastic.co/t/decomissioning-node-question-does-not-start-moving-shards/94624 "2017-07-26T11:11:49Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@uschellh](https://discuss.elastic.co/u/uschellh)
#### Post date: [July 26, 2017, 11:11am UTC](https://discuss.elastic.co/t/decomissioning-node-question-does-not-start-moving-shards/94624/1 "2017-07-26T11:11:49Z")
Hello,
we want to decomission nodes, i already excluded those nodes from allocation:
"cluster.routing.allocation.exclude.\_name"
ans also configured each index for the node where it should land (it will be 1 remaining one)
"index.routing.allocation.include.\_name"
thats ok so far, but now i dont see shards relocate.
if i issue
curl -XPUT [http://localhost:9200/\_cluster/reroute](http://localhost:9200/_cluster/reroute) {"commands": [{ "move": { "index": "logstash-2017.06.02", "shard": 1, "from\_node": "A", "to\_node": "B" }}]}
i get the following error:
{"error":{"root\_cause":[{"type":"remote\_transport\_exception","reason":"
[Fufluns][34.52.56.45:9300][cluster:admin/reroute]"}],"type":
"illegal\_argument\_exception","reason":"[move\_allocation] can't move 1,
from {bacchus}{WaYtCc6yToeYYV\_27SBz1g}{6fx-t1-oQ\_iHrq\_0elxawA}{34.52.56.101}{34.52.56.101:9300},
to {dionysios}{Evs6ZXrhRoin1WryAQdqhw}{QFkKtWzwSBeco-sec-OqDg}{34.52.56.36}{34.52.56.36:9300},
since its not allowed, reason:
[YES(shard has no previous failures)]
[YES(shard is primary and can be allocated)]
[YES(explicitly ignoring any disabling of allocation due to manual allocation commands via the reroute API)]
[YES(target node version [5.5.0] is the same or newer than source node version [5.5.0])]
[YES(no snapshots are currently running)]
[YES(node passes include/exclude/require filters)]
[NO(the shard cannot be allocated to the same node on which a copy of the shard already exists
[[logstash-2017.06.02][1], node[Evs6ZXrhRoin1WryAQdqhw], [R], s[STARTED], a[id=eIzWZl4mSVmX5\_sQonrWnQ]])]
[YES(enough disk for shard on node, free: [1.6tb], shard size: [11.7kb], free after allocating shard: [1.6tb])][THROTTLE(reached the limit of incoming shard recoveries [2], cluster setting [cluster.routing.allocation.node\_concurrent\_incoming\_recoveries=2] (can also be set via [cluster.routing.allocation.node\_concurrent\_recoveries]))]
[YES(total shard limits are disabled: [index: -1, cluster: -1] \<= 0)]
[YES(allocation awareness is not enabled, set cluster setting [cluster.routing.allocation.awareness.attributes] to enable it)]"},"status":400}
how would i go about forcing the nodes to release their data and be able to shut them down ?
thanks !
---
### Author:  [@uschellh](https://discuss.elastic.co/u/uschellh)
#### Post date: [August 3, 2017, 10:45am UTC](https://discuss.elastic.co/t/decomissioning-node-question-does-not-start-moving-shards/94624/2 "2017-08-03T10:45:27Z")
Hello,
it took some days (ended today), seems to be a low prio job.
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [August 4, 2017, 7:14am UTC](https://discuss.elastic.co/t/decomissioning-node-question-does-not-start-moving-shards/94624/3 "2017-08-04T07:14:41Z")
Hey,
the error message indicates, that the node you wanted to move the shard to already had a replica of that shard
```auto
[NO(the shard cannot be allocated to the same node on which a copy of the shard already exists
[[logstash-2017.06.02][1], node[Evs6ZXrhRoin1WryAQdqhw], [R], s[STARTED], a[id=eIzWZl4mSVmX5_sQonrWnQ]])]
```
your assumption on top of that is right, because of the following message
```auto
[THROTTLE(reached the limit of incoming shard recoveries [2], cluster setting
```
a cluster wide setting to limit the concurrent shard recoveries. If you have many shards, than this might be the limiting factor.
--Alex
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 1, 2017, 7:14am UTC](https://discuss.elastic.co/t/decomissioning-node-question-does-not-start-moving-shards/94624/4 "2017-09-01T07:14:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.