# Contact for solutions when index lifecycle policies are not reflected

**URL:** <https://discuss.elastic.co/t/contact-for-solutions-when-index-lifecycle-policies-are-not-reflected/374913>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [February 24, 2025, 3:57am UTC](https://discuss.elastic.co/t/contact-for-solutions-when-index-lifecycle-policies-are-not-reflected/374913 "2025-02-24T03:57:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sjoh9163](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sjoh9163/32/141576_2.png) [@sjoh9163](https://discuss.elastic.co/u/sjoh9163)\
**Post date:** [February 24, 2025, 3:57am UTC](https://discuss.elastic.co/t/contact-for-solutions-when-index-lifecycle-policies-are-not-reflected/374913/1 "2025-02-24T03:57:53Z")

</div>

I am using ECK 8.14 and here is the reflected Index Lifecycle Policies(ILM) content:

```auto
PUT _ilm/policy/ECK-ILM
{
  "policy": {
    "phases": {
      "hot": {
        "min_age": "0ms",
        "actions": {
          "set_priority": {
            "priority": 100
          },
          "rollover": {
            "max_age": "7d",
            "max_docs": 7,
            "max_primary_shard_size": "30gb",
            "max_size": "5gb"
          }
        }
      },
      "warm": {
        "min_age": "7d",
        "actions": {
          "set_priority": {
            "priority": 50
          }
        }
      },
      "delete": {
        "min_age": "7d",
        "actions": {
          "delete": {
            "delete_searchable_snapshot": true
          }
        }
      }
    }
  }
}

```

However, in reality, the above policy does not seem to be reflected.

 ![스크린샷 2025-02-24 125233](https://us1.discourse-cdn.com/elastic/original/3X/8/9/898a2584e278d759aa5bf0b62a2d2a5ecad8b328.png)

I added the ILM policy, but it doesn't seem to be reflected. I'm writing this to get help on how to secure capacity as capacity is saturated. Please clear it manually or let me know if I missed something in the settings.

---

<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:** [February 24, 2025, 4:58am UTC](https://discuss.elastic.co/t/contact-for-solutions-when-index-lifecycle-policies-are-not-reflected/374913/2 "2025-02-24T04:58:19Z")

</div>

Hi @sjoh9163 Welcome to the community.

According to the image looks like the ILM is actually policy applied.

Click on this

 ![1000005018](https://us1.discourse-cdn.com/elastic/original/3X/8/7/87f6a33f3c1f75f6fad2373baaf3190374ae3d5d.jpeg)

And show the results it will show the backing indices for the data stream

BTW `max_size` is not recommended and is in conflict with the `max_primary_shard_size`

---

<div class="post-metadata">

**Author:** ![sjoh9163](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sjoh9163/32/141576_2.png) [@sjoh9163](https://discuss.elastic.co/u/sjoh9163)\
**Post date:** [February 24, 2025, 5:29am UTC](https://discuss.elastic.co/t/contact-for-solutions-when-index-lifecycle-policies-are-not-reflected/374913/3 "2025-02-24T05:29:54Z")

</div>

Thanks Mr. Brown.  
It may be a crash issue as you said.  
I changed ILM policy to the following:

```auto
PUT _ilm/policy/ECK-ILM
{
  "policy": {
    "phases": {
      "hot": {
        "min_age": "0ms",
        "actions": {
          "set_priority": {
            "priority": 100
          },
          "rollover": {
            "max_primary_shard_size": "5gb"
          }
        }
      }
    }
  }
}

```

I hope this is the solution.

---

<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:** [February 24, 2025, 3:08pm UTC](https://discuss.elastic.co/t/contact-for-solutions-when-index-lifecycle-policies-are-not-reflected/374913/4 "2025-02-24T15:08:38Z")

</div>

> [@sjoh9163](#):
>
> ` "max_primary_shard_size": "5gb"`

That is very small, especially for logs... should be between 30-50gb

and what happened to your warm and delete.

You should also look at this API to diagnose issues with ILM

> **[Explain lifecycle API | Elasticsearch Guide \[8.17\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-explain-lifecycle.html)**

If you still have issues, run that command on the index with the issues, and we can debug it