# ILM rollover not working on max\_size?

**URL:** <https://discuss.elastic.co/t/ilm-rollover-not-working-on-max-size/287999>\
**Category:** Elasticsearch\
**Created:** [October 29, 2021, 1:05pm UTC](https://discuss.elastic.co/t/ilm-rollover-not-working-on-max-size/287999 "2021-10-29T13:05:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [October 31, 2021, 3:14pm UTC](https://discuss.elastic.co/t/ilm-rollover-not-working-on-max-size/287999/4 "2021-10-31T15:14:31Z")

</div>

Rollover should be typically thought of in terms of GBs not MBs so the _overage_ in true production systems tend to be a small percentage. This does have some relationship to indexing rate.

ILM is not built as @dadoonet said to rollover on exact byte counts it is a background task.

---

_[View the full topic](https://discuss.elastic.co/t/ilm-rollover-not-working-on-max-size/287999)._