Contact for solutions when index lifecycle policies are not reflected

Elastic Stack Elasticsearch
1

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

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
스크린샷 2025-02-24 125233719×810 57.3 KB

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.

2

Hi @sjoh9163 Welcome to the community.

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

Click on this

1000005018
1000005018864×1920 118 KB

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

1 Like
3

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

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.

4

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

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

1 Like