# Unbalanced disk usage - ES 2.1 **URL:** \ **Category:** Elasticsearch\ **Created:** [May 9, 2018, 7:03pm UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219 "2018-05-09T19:03:45Z")\ **Posts on this page:** 11\ **Page:** 2
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [May 10, 2018, 6:59pm UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219/21 "2018-05-10T18:59:55Z")
I do not know. Have not used Elasticsearch 2.x in a long time... ---
**Author:** ![Wedney\_Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wedney_yuri/32/22706_2.png) [@Wedney\_Yuri](https://discuss.elastic.co/u/Wedney_Yuri)\ **Post date:** [May 10, 2018, 9:52pm UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219/22 "2018-05-10T21:52:42Z")
In your case seems to be related to [https://github.com/elastic/elasticsearch/pull/29125](https://github.com/elastic/elasticsearch/pull/29125) which was fixed in version 6.2.4. We also noticed a huge increase in open file descriptors: ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/1/e1f632fc2063abcb2bd9625c368c24511a0b48c6.png) ---
**Author:** ![farin99](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/farin99/32/27873_2.png) [@farin99](https://discuss.elastic.co/u/farin99)\ **Post date:** [May 16, 2018, 8:33am UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219/23 "2018-05-16T08:33:28Z")
Hi, @Wedney_Yuri I think the issue you described is related to [https://github.com/elastic/elasticsearch/issues/29488](https://github.com/elastic/elasticsearch/issues/29488). We are experiencing a similar issue with 6.2.4 as described in [https://github.com/elastic/elasticsearch/issues/30351](https://github.com/elastic/elasticsearch/issues/30351) Hopefully, the following merge that will be release in 6.3.0 will solve the issue: > ---
**Author:** ![Wedney\_Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wedney_yuri/32/22706_2.png) [@Wedney\_Yuri](https://discuss.elastic.co/u/Wedney_Yuri)\ **Post date:** [May 16, 2018, 2:11pm UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219/24 "2018-05-16T14:11:28Z")
Thank you, I will investigate. ---
**Author:** ![Wedney\_Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wedney_yuri/32/22706_2.png) [@Wedney\_Yuri](https://discuss.elastic.co/u/Wedney_Yuri)\ **Post date:** [May 30, 2018, 1:22pm UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219/25 "2018-05-30T13:22:10Z")
You're right, we're noticing full disk usage in version 6.2.4. How did you solve this problem? ---
**Author:** ![farin99](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/farin99/32/27873_2.png) [@farin99](https://discuss.elastic.co/u/farin99)\ **Post date:** [May 30, 2018, 1:44pm UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219/26 "2018-05-30T13:44:46Z")
As far as I know there is no solution and we are left to wait for 6.3.0 to be released. Calling force merge didn't help. The only two things that cause the shards to shrink were: 1. Closing and reopen the index 2. Restart the node that the shards is on These actions will force elastic to initialize the shards and only then it will run a successful merge on these shards. Both are not a valid workaround ☹ Note that the initialize of these shards can take ages depends on the shard size, during this time the data in these shards won't be accessible. ---
**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:** [May 30, 2018, 2:56pm UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219/27 "2018-05-30T14:56:12Z")
> [@farin99](#): > > The only two things that cause the shards to shrink were... It should be sufficient to set the number of replicas to zero and back to 1, which will cause the replicas to be reinitialised. It is also even possible to use the [reroute API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-reroute.html) to cancel the allocation of the problematic replica which will cause just that one shard to be rebuilt. ---
**Author:** ![farin99](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/farin99/32/27873_2.png) [@farin99](https://discuss.elastic.co/u/farin99)\ **Post date:** [May 30, 2018, 3:19pm UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219/28 "2018-05-30T15:19:59Z")
In our case, the shards that didn't perform merge operations were the primaries and removing the replicas didn't do the trick. ---
**Author:** ![Wedney\_Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wedney_yuri/32/22706_2.png) [@Wedney\_Yuri](https://discuss.elastic.co/u/Wedney_Yuri)\ **Post date:** [May 30, 2018, 3:55pm UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219/29 "2018-05-30T15:55:56Z")
As @farin99 said, it's happening to primary nodes as well. This has been happening almost every day, do you know which is the last stable version of elasticsearch that was released without this bug? ---
**Author:** ![Wedney\_Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wedney_yuri/32/22706_2.png) [@Wedney\_Yuri](https://discuss.elastic.co/u/Wedney_Yuri)\ **Post date:** [May 30, 2018, 6:06pm UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219/30 "2018-05-30T18:06:21Z")
@farin99 I don't know why, but we changed `indices.recovery.max_bytes_per_sec` to 4000mb and the disk usage was reduced after minutes. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 27, 2018, 6:06pm UTC](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219/31 "2018-06-27T18:06:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed. [Previous page](https://discuss.elastic.co/t/unbalanced-disk-usage-es-2-1/131219.md?page=1)