# /\_cluster/reroute doesn't respect node\_concurrent\_recoveries **URL:** \ **Category:** Elasticsearch\ **Created:** [December 28, 2019, 1:04am UTC](https://discuss.elastic.co/t/cluster-reroute-doesnt-respect-node-concurrent-recoveries/213238 "2019-12-28T01:04:26Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![dwilches](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dwilches/32/48586_2.png) [@dwilches](https://discuss.elastic.co/u/dwilches)\ **Post date:** [December 28, 2019, 1:04am UTC](https://discuss.elastic.co/t/cluster-reroute-doesnt-respect-node-concurrent-recoveries/213238/1 "2019-12-28T01:04:26Z")
I have 4 nodes in my cluster: A,B,C,D,E,F and G. I'm issuing a series of `/_cluster/reroute` commands to move 2 shards out of A,B,C,D,E,F into G. As my cluster's config says: ```auto cluster.routing.allocation.node_concurrent_incoming_recoveries => 2 cluster.routing.allocation.node_concurrent_outgoing_recoveries => 2 cluster.routing.allocation.node_concurrent_recoveries => 8 ``` I was expecting G to only be able to receive either 2 or 8 shards in parallel, but instead, the cluster allowed the 12 shards to be moved at the same time as I could see the status as `RELOCATING` in `/_cat/shards`. Is this expected behaviour? if so, what is the config parameter I need to change to limit how many shards my cluster can move in parallel when I use the `_cluster/reroute` command? Thanks. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 25, 2020, 1:04am UTC](https://discuss.elastic.co/t/cluster-reroute-doesnt-respect-node-concurrent-recoveries/213238/2 "2020-01-25T01:04:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.