# ILM Policy is not working

**URL:** <https://discuss.elastic.co/t/ilm-policy-is-not-working/289465>\
**Category:** Kibana\
**Tags:** ilm-index-lifecycle-management\
**Created:** [November 17, 2021, 2:49pm UTC](https://discuss.elastic.co/t/ilm-policy-is-not-working/289465 "2021-11-17T14:49:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![maltewhiite](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maltewhiite/32/94551_2.png) [@maltewhiite](https://discuss.elastic.co/u/maltewhiite)\
**Post date:** [November 17, 2021, 2:49pm UTC](https://discuss.elastic.co/t/ilm-policy-is-not-working/289465/1 "2021-11-17T14:49:32Z")

</div>

I have an Index Lifecycle Management Policy using a Hot Phase with recommended defaults. So Roll over when an index is 30 days old or any primary shard reaches 50 gigabytes.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/1/61ad190b5db033189647d1b803158326e161c58e.png)  
I assume this means that the index is converted from 000001 to 000002 whenever it hits 50 gb.

I then have an index template with the ILM policy tied to it.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/7/d7b4ff25cf093ed7d6e6613436932b2c2a561975.png)

I then have an Index which isn't rolling over at 50gb+

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/a/aa7a52733bf3f677f01b5ef700a20d0e7f9c65f0.png)  
Here is the Index summary:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/1/e14527ac173c71fd123158b1643af07c320d2305.png)

Why is it not making a new filebeat-7.13.2-000002 index and writing to that automatically?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 17, 2021, 11:36pm UTC](https://discuss.elastic.co/t/ilm-policy-is-not-working/289465/2 "2021-11-17T23:36:26Z")

</div>

The rollover is based on the **primary** shard size, and you're seeing the combined size of both primary **and** replica.

---

<div class="post-metadata">

**Author:** ![maltewhiite](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maltewhiite/32/94551_2.png) [@maltewhiite](https://discuss.elastic.co/u/maltewhiite)\
**Post date:** [November 18, 2021, 8:20am UTC](https://discuss.elastic.co/t/ilm-policy-is-not-working/289465/3 "2021-11-18T08:20:39Z")

</div>

Ahh, okay. Did I miss this in the documentation or in the Kibana UI somewhere?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 19, 2021, 4:05am UTC](https://discuss.elastic.co/t/ilm-policy-is-not-working/289465/4 "2021-11-19T04:05:52Z")

</div>

Yeah it's not super clear. I raised [Add tooltip to ILM Storage Size information · Issue #118976 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/118976) to address that.

---

<div class="post-metadata">

**Author:** ![maltewhiite](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maltewhiite/32/94551_2.png) [@maltewhiite](https://discuss.elastic.co/u/maltewhiite)\
**Post date:** [November 19, 2021, 3:00pm UTC](https://discuss.elastic.co/t/ilm-policy-is-not-working/289465/5 "2021-11-19T15:00:21Z")

</div>

Thank you Mark.  
Have a nice weekend.

---

<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:** [December 17, 2021, 3:00pm UTC](https://discuss.elastic.co/t/ilm-policy-is-not-working/289465/6 "2021-12-17T15:00:43Z")

</div>

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