# Any risks with self scheduling balancing?

**URL:** <https://discuss.elastic.co/t/any-risks-with-self-scheduling-balancing/91155>\
**Category:** Elasticsearch\
**Created:** [June 28, 2017, 5:08pm UTC](https://discuss.elastic.co/t/any-risks-with-self-scheduling-balancing/91155 "2017-06-28T17:08:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eli\_Revach](https://avatars.discourse-cdn.com/v4/letter/e/e9c0ed/32.png) [@Eli\_Revach](https://discuss.elastic.co/u/Eli_Revach)\
**Post date:** [June 28, 2017, 5:08pm UTC](https://discuss.elastic.co/t/any-risks-with-self-scheduling-balancing/91155/1 "2017-06-28T17:08:43Z")

</div>

Hi  
We are using ES=.1.7.5

We are facing from time to time GC old GEN , leading to cluster balancing.  
The balancing consume high resource from the cluster , so i consider the below procedure until we will find the root cause of the GC.

1. disable balancing- (cluster.routing.allocation.balance.threshold" : "100.0f")

2. schedule external daily job that will run ES API to Enable it for duration of 1 hour in a day ( let say between 8-9AM ) using "cluster.routing.allocation.balance.threshold" : "1.0f" (Return to Default)

3. Disable it back after 1 hour

Any risk ?

Thanks

---

<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:** [July 26, 2017, 5:08pm UTC](https://discuss.elastic.co/t/any-risks-with-self-scheduling-balancing/91155/2 "2017-07-26T17:08:51Z")

</div>

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