# ILM rollover when max\_docs reached

**URL:** <https://discuss.elastic.co/t/ilm-rollover-when-max-docs-reached/360455>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [May 29, 2024, 11:25am UTC](https://discuss.elastic.co/t/ilm-rollover-when-max-docs-reached/360455 "2024-05-29T11:25:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [May 29, 2024, 11:57am UTC](https://discuss.elastic.co/t/ilm-rollover-when-max-docs-reached/360455/2 "2024-05-29T11:57:54Z")

</div>

> [@vincent2mots](#):
>
> I would like to create a ILM policy which would create a new index each time the previous one reached 30 documents.

The default settings for ILM are set up for realistic workloads. It therefore only checks for rollover every 10 minutes or so. This is perfect for real scenarios but means that small scale unrealistic tests do not work as expected.

Either run a more realistic test or change the settings to something that is not suitable for real-world use cases.

---

_[View the full topic](https://discuss.elastic.co/t/ilm-rollover-when-max-docs-reached/360455)._