# Elasticsearch Index Rollover

**URL:** <https://discuss.elastic.co/t/elasticsearch-index-rollover/205763>\
**Category:** Elasticsearch\
**Created:** [October 29, 2019, 10:33pm UTC](https://discuss.elastic.co/t/elasticsearch-index-rollover/205763 "2019-10-29T22:33:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![eemtzc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eemtzc/32/54095_2.png) [@eemtzc](https://discuss.elastic.co/u/eemtzc)\
**Post date:** [October 29, 2019, 10:33pm UTC](https://discuss.elastic.co/t/elasticsearch-index-rollover/205763/1 "2019-10-29T22:33:13Z")

</div>

I have a problem, for some reason the previous Elasticsearch Admin configured an Index in a way that this index does not create a daily rollout. I will explain this better:  
I have a filebeat index running and every single day it create an index like this:  
filebeat-7.4.0-2019-10-29  
filebeat-7.4.0-2019-10-28  
filebeat-7.4.0-2019-10-27  
filebeat-7.4.0-2019-10-26  
.  
.  
.  
but the index that I am talking about, does not create this kind of break down I only have an thisisanIndex, right now, because of this I'm in a big problem since this index is using 1.3Tb of space and I cannot delete old indeces.  
Do you know if there is a way I can configure this index to make that rollover every day? or how can I delete somo of the docs on this index to free some space in my cluster.

---

<div class="post-metadata">

**Author:** ![HenningAndersen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/henningandersen/32/48188_2.png) [@HenningAndersen](https://discuss.elastic.co/u/HenningAndersen)\
**Post date:** [October 30, 2019, 12:26pm UTC](https://discuss.elastic.co/t/elasticsearch-index-rollover/205763/2 "2019-10-30T12:26:36Z")

</div>

Hi @eemtzc,

I would recommend you to look into [index lifecycle management](https://www.elastic.co/guide/en/elasticsearch/reference/master/index-lifecycle-management.html), which can do the roll over automatically.

---

<div class="post-metadata">

**Author:** ![eemtzc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eemtzc/32/54095_2.png) [@eemtzc](https://discuss.elastic.co/u/eemtzc)\
**Post date:** [October 30, 2019, 5:50pm UTC](https://discuss.elastic.co/t/elasticsearch-index-rollover/205763/3 "2019-10-30T17:50:05Z")

</div>

Thank you for your response, just to be sure, ILM will be able to break that huge index of 1.2 Tb into smaller indices by day so I can delete the old ones?

---

<div class="post-metadata">

**Author:** ![bruce289](https://avatars.discourse-cdn.com/v4/letter/b/7bcc69/32.png) [@bruce289](https://discuss.elastic.co/u/bruce289)\
**Post date:** [October 30, 2019, 7:11pm UTC](https://discuss.elastic.co/t/elasticsearch-index-rollover/205763/4 "2019-10-30T19:11:04Z")

</div>

> [@eemtzc](#):
>
> Thank you for your response, just to be sure, ILM will be able to break that huge index of 1.2 Tb into smaller indices by day so I can delete the old ones?

It will help for any future indices, but not for the existing huge one. For that, you should look at [reindexing](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html) through a pipeline that uses the [Date Index Name Processor](https://www.elastic.co/guide/en/elasticsearch/reference/current/date-index-name-processor.html).

Alternatively, you could [Reindex into an ILM alias](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-reindexing-into-rollover.html)

---

<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:** [November 27, 2019, 7:11pm UTC](https://discuss.elastic.co/t/elasticsearch-index-rollover/205763/5 "2019-11-27T19:11:12Z")

</div>

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