# Remove a Node controlling the number of shards reallocating

**URL:** <https://discuss.elastic.co/t/remove-a-node-controlling-the-number-of-shards-reallocating/171765>\
**Category:** Elasticsearch\
**Created:** [March 11, 2019, 12:48pm UTC](https://discuss.elastic.co/t/remove-a-node-controlling-the-number-of-shards-reallocating/171765 "2019-03-11T12:48:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Javier\_Parrondo](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@Javier\_Parrondo](https://discuss.elastic.co/u/Javier_Parrondo)\
**Post date:** [March 11, 2019, 12:48pm UTC](https://discuss.elastic.co/t/remove-a-node-controlling-the-number-of-shards-reallocating/171765/1 "2019-03-11T12:48:29Z")

</div>

Hello,

At the moment on which I want to remove a node inside a Elasticsearch cluster I was wondering if there is possible to controll how many shards are going to be reallocating at the same time, I know the cluster setting called "cluster.routing.allocation.cluster\_concurrent\_rebalance" but inside the documentation I could read that this settings does not apply when I want to remove a node with the following setting:

cluster.routing.allocation.exclude.{attribute}

Do you have any idea about this issue?

Thanks for all.  
Best Regards

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [March 11, 2019, 1:23pm UTC](https://discuss.elastic.co/t/remove-a-node-controlling-the-number-of-shards-reallocating/171765/2 "2019-03-11T13:23:35Z")

</div>

If you apply a shard allocation filter with `cluster.routing.allocation.exclude.{attribute}` then the shards are relocated elsewhere using the [recovery mechanism](https://www.elastic.co/guide/en/elasticsearch/reference/6.6/indices-recovery.html). This means you can set [`cluster.routing.allocation.node_concurrent_recoveries`](https://www.elastic.co/guide/en/elasticsearch/reference/current/shards-allocation.html#_shard_allocation_settings) to limit the number of recoveries happening at each node, and [`indices.recovery.max_bytes_per_sec`](https://www.elastic.co/guide/en/elasticsearch/reference/6.6/recovery.html#recovery) to limit the bandwidth used by recoveries.

---

<div class="post-metadata">

**Author:** ![Javier\_Parrondo](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@Javier\_Parrondo](https://discuss.elastic.co/u/Javier_Parrondo)\
**Post date:** [March 11, 2019, 5:50pm UTC](https://discuss.elastic.co/t/remove-a-node-controlling-the-number-of-shards-reallocating/171765/3 "2019-03-11T17:50:24Z")

</div>

Hi David

Thanks for all, I have tried this and works fine!

Thanks again!

---

<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:** [April 8, 2019, 5:50pm UTC](https://discuss.elastic.co/t/remove-a-node-controlling-the-number-of-shards-reallocating/171765/4 "2019-04-08T17:50:37Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.