# How to manage elasticsearch data directory

**URL:** <https://discuss.elastic.co/t/how-to-manage-elasticsearch-data-directory/97452>\
**Category:** Elasticsearch\
**Created:** [August 17, 2017, 3:42pm UTC](https://discuss.elastic.co/t/how-to-manage-elasticsearch-data-directory/97452 "2017-08-17T15:42:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohit214721](https://avatars.discourse-cdn.com/v4/letter/m/9fc29f/32.png) [@mohit214721](https://discuss.elastic.co/u/mohit214721)\
**Post date:** [August 17, 2017, 3:42pm UTC](https://discuss.elastic.co/t/how-to-manage-elasticsearch-data-directory/97452/1 "2017-08-17T15:42:11Z")

</div>

I am using ELK stack in UAT environment along with the filebeat functionality (installed in various webservers).

While using it, i could see that directory /elasticsearch-5.2.2/data/nodes directory is getting increased drastically which results in crashing the server where elasticsearch is installed. So is there any way to handle such big data automatically . I am very new to elasticsearch. What i want to delete the older data indices automatically in regular intervals.

---

<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:** [August 18, 2017, 2:35am UTC](https://discuss.elastic.co/t/how-to-manage-elasticsearch-data-directory/97452/2 "2017-08-18T02:35:51Z")

</div>

FYI we’ve renamed ELK to the Elastic Stack, otherwise Beats feels left out 😉

> [@mohit214721](#):
>
> While using it, i could see that directory /elasticsearch-5.2.2/data/nodes directory is getting increased drastically which results in crashing the server where elasticsearch is installed.

Why does it crash what is the log?

You can use [Elasticsearch Curator](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html) to manage indices.

---

<div class="post-metadata">

**Author:** ![mohit214721](https://avatars.discourse-cdn.com/v4/letter/m/9fc29f/32.png) [@mohit214721](https://discuss.elastic.co/u/mohit214721)\
**Post date:** [August 18, 2017, 5:51am UTC](https://discuss.elastic.co/t/how-to-manage-elasticsearch-data-directory/97452/3 "2017-08-18T05:51:20Z")

</div>

Thanks for your reply. It is being crashed because of 100 % disk utilization as data/nodes directory is getting increased in size quickly. 50 GB is consumed in a day.

Also, Can you please help me to use elasticsearch curator step by step as i am very new to this. Will it manage the indices logs automatically?

---

<div class="post-metadata">

**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:** [August 18, 2017, 6:03am UTC](https://discuss.elastic.co/t/how-to-manage-elasticsearch-data-directory/97452/4 "2017-08-18T06:03:52Z")

</div>

The space data takes up on disk will depend on your mappings, and you can often save a lot of space by optimising these. This is discussed in [this blog post](https://www.elastic.co/blog/filebeat-modiles-access-logs-and-elasticsearch-storage-requirements) as well as in [the documentation](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/tune-for-disk-usage.html#tune-for-disk-usage).

---

<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:** [September 15, 2017, 6:04am UTC](https://discuss.elastic.co/t/how-to-manage-elasticsearch-data-directory/97452/5 "2017-09-15T06:04:15Z")

</div>

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