# Filebeat deleted indecies are getting recreated due to no log rotation policy

**URL:** <https://discuss.elastic.co/t/filebeat-deleted-indecies-are-getting-recreated-due-to-no-log-rotation-policy/206064>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [October 31, 2019, 2:51pm UTC](https://discuss.elastic.co/t/filebeat-deleted-indecies-are-getting-recreated-due-to-no-log-rotation-policy/206064 "2019-10-31T14:51:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ankamraok](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankamraok/32/49498_2.png) [@ankamraok](https://discuss.elastic.co/u/ankamraok)\
**Post date:** [October 31, 2019, 2:51pm UTC](https://discuss.elastic.co/t/filebeat-deleted-indecies-are-getting-recreated-due-to-no-log-rotation-policy/206064/1 "2019-10-31T14:51:48Z")

</div>

Hi All,  
I have a log which can only rotate after reaching 100 MB,and this log is pretty slow and it might reaches 100 MB by 6 months,though it generates log messages every hour.it has 3 months data.

I have a curator which deletes all the indecies older than 30 days but when this log gets new messages,all the older indecies for last 3 months(one idex per day)getting created.

Could you please suggest me how to handle this

---

<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 28, 2019, 2:51pm UTC](https://discuss.elastic.co/t/filebeat-deleted-indecies-are-getting-recreated-due-to-no-log-rotation-policy/206064/2 "2019-11-28T14:51:54Z")

</div>

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