# Elasticsearch no disk space available

**URL:** <https://discuss.elastic.co/t/elasticsearch-no-disk-space-available/33466>\
**Category:** Elasticsearch\
**Created:** [November 1, 2015, 1:47pm UTC](https://discuss.elastic.co/t/elasticsearch-no-disk-space-available/33466 "2015-11-01T13:47:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Isaac\_Hazan](https://avatars.discourse-cdn.com/v4/letter/i/a5b964/32.png) [@Isaac\_Hazan](https://discuss.elastic.co/u/Isaac_Hazan)\
**Post date:** [November 1, 2015, 1:47pm UTC](https://discuss.elastic.co/t/elasticsearch-no-disk-space-available/33466/1 "2015-11-01T13:47:58Z")

</div>

I have a 3 nodes Elasticsearch cluster that exhausted the disk space in each node. Each node is an EC2 instance. The cluster is now completely irresponsive.

What solutions do I have to free up space?

Would adding a node in cluster free up space in the other node because now the cluster will re-distribute the information over the other nodes?

Or is my only solution but definitely not the preferred ones is to create a larger cluster on the side and migrate over the data from the first cluster?

Any other ideas/solutions is more than welcome.

The cluster configuration on each node(elasticsearch.yml) looks as follows:

```
cluster.name: AutoSearchCluster
node.name: i-asd4352
plugin.mandatory: cloud-aws
discovery.zen.ping.multicast.enabled: false
discovery.type: ec2
cloud.aws.region: us-west-2
discovery.ec2.groups: prod-group
gateway.recover_after_nodes: 2
gateway.expected_nodes: 3
gateway.recover_after_time: 5m
indices.fielddata.cache.size: 40%
```

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [November 1, 2015, 2:48pm UTC](https://discuss.elastic.co/t/elasticsearch-no-disk-space-available/33466/2 "2015-11-01T14:48:28Z")

</div>

Please edit your post and move it to the "Elasticsearch" category. The "Elastic User Groups" category is meant for something else.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 1, 2015, 8:12pm UTC](https://discuss.elastic.co/t/elasticsearch-no-disk-space-available/33466/3 "2015-11-01T20:12:23Z")

</div>

> [@Isaac\_Hazan](#):
>
> Would adding a node in cluster free up space in the other node because now the cluster will re-distribute the information over the other nodes?

It will.

You should also look at [Elasticsearch Curator](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html) to manage your data.

---

<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 5, 2017, 11:41pm UTC](https://discuss.elastic.co/t/elasticsearch-no-disk-space-available/33466/4 "2017-07-05T23:41:27Z")

</div>