# 20GB disk space consumed in a few minutes **URL:** \ **Category:** Elasticsearch\ **Created:** [March 8, 2017, 5:41pm UTC](https://discuss.elastic.co/t/20gb-disk-space-consumed-in-a-few-minutes/77863 "2017-03-08T17:41:45Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Mariano\_Matayoshi](https://avatars.discourse-cdn.com/v4/letter/m/9fc29f/32.png) [@Mariano\_Matayoshi](https://discuss.elastic.co/u/Mariano_Matayoshi)\ **Post date:** [March 8, 2017, 5:41pm UTC](https://discuss.elastic.co/t/20gb-disk-space-consumed-in-a-few-minutes/77863/1 "2017-03-08T17:41:45Z")
Hi! First of all, I have searched and read every post about this, but I could not found anything in particulary. It's been two months since I have integrated AWS ES service in my application, and three times happened this: There is a time when the index start consuming all the disk space. The last time the index was about 30GB AWS ES service config: - Data node: 2 - Data node types: m3.medium.elasticsearch - Dedicated master instance count: 3 - Dedicated master instance type: t2.small.elasticsearch. - Capacity of each data node: 100GB. - ES version: 2.3 The problem is that in less than thirty minutes one of the node free storage size went from 21 GB to 0 GB, we did not know how this happened. I am thinking that a merge happened, but I am not sure. I have attached the a graph of the minimum free storage space ![](https://us1.discourse-cdn.com/elastic/original/3X/3/5/356a39b1f4a2dd175a854402a5e5d9393e594bb5.png) Thanks in advance! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 5, 2017, 5:42pm UTC](https://discuss.elastic.co/t/20gb-disk-space-consumed-in-a-few-minutes/77863/2 "2017-04-05T17:42:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.