# ILM policy is not followed correctly and index is not getting rollover as per doc size or max age

**URL:** https://discuss.elastic.co/t/ilm-policy-is-not-followed-correctly-and-index-is-not-getting-rollover-as-per-doc-size-or-max-age/312306
**Category:** Kibana
**Tags:** ilm-index-lifecycle-management
**Created:** [August 17, 2022, 4:06pm UTC](https://discuss.elastic.co/t/ilm-policy-is-not-followed-correctly-and-index-is-not-getting-rollover-as-per-doc-size-or-max-age/312306 "2022-08-17T16:06:07Z")
**Posts on this page:** 1
**Showing post:** 3

<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: [August 18, 2022, 3:08am UTC](https://discuss.elastic.co/t/ilm-policy-is-not-followed-correctly-and-index-is-not-getting-rollover-as-per-doc-size-or-max-age/312306/3 "2022-08-18T03:08:01Z")

</div>

Hi @PRASHANT_MEHTA Those sizes and timeframes are too short..

ILM is not really design to operate on "Minute" Scheduled or Small KB/MB indices is designed to manage large scale indices GB, Hours, Days etc. and for that it works very well.

I posted a bit about it [here](https://discuss.elastic.co/t/rollover-goes-beyond-the-condition/207442/2) and another elastician [here](https://discuss.elastic.co/t/lifecycle-policies-dont-work/276218/13)

---

_[View the full topic](https://discuss.elastic.co/t/ilm-policy-is-not-followed-correctly-and-index-is-not-getting-rollover-as-per-doc-size-or-max-age/312306)._