# ILM problem

**URL:** <https://discuss.elastic.co/t/ilm-problem/373646>\
**Category:** Beats\
**Tags:** winlogbeat\
**Created:** [January 24, 2025, 6:48pm UTC](https://discuss.elastic.co/t/ilm-problem/373646 "2025-01-24T18:48:35Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [January 24, 2025, 7:06pm UTC](https://discuss.elastic.co/t/ilm-problem/373646/2 "2025-01-24T19:06:27Z")

</div>

Hi @Mehran_Noorani Welcome to the community!

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)

ILM by default only checks every 10 minutes. I believe so. We often see people trying to test like this. It's not designed to work at these micro scales.. It works at the scale that it's supposed to very well

---

_[View the full topic](https://discuss.elastic.co/t/ilm-problem/373646)._