# Disabling all the relocation that is happening in the cluster

**URL:** <https://discuss.elastic.co/t/disabling-all-the-relocation-that-is-happening-in-the-cluster/141989>\
**Category:** Elasticsearch\
**Created:** [July 27, 2018, 7:46pm UTC](https://discuss.elastic.co/t/disabling-all-the-relocation-that-is-happening-in-the-cluster/141989 "2018-07-27T19:46:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fhalde](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fhalde/32/21419_2.png) [@fhalde](https://discuss.elastic.co/u/fhalde)\
**Post date:** [July 27, 2018, 7:46pm UTC](https://discuss.elastic.co/t/disabling-all-the-relocation-that-is-happening-in-the-cluster/141989/1 "2018-07-27T19:46:25Z")

</div>

We have a 2.4 cluster.

We excluded few nodes for certain indices using the exclude setting in our cluster which triggered a relo of 220 shards. we had concurrent\_rebalance set to 2 but it didnt take any effect. Is there a way to disabled all this rebalancing that is happening?

will cluster.routing.rebalance.enabled: none help?

also what is generic threadpool used for ? is it for the above rebalance? we see 100+ threads being used by that threadpool?

---

<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:** [August 24, 2018, 7:46pm UTC](https://discuss.elastic.co/t/disabling-all-the-relocation-that-is-happening-in-the-cluster/141989/2 "2018-08-24T19:46:44Z")

</div>

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