Rollover between lifecycle states

Hello,

I have configured my indexes to work with ILM policy to automatically move between states like hot and warm. Also I want them to get automatically removed when they get too old. For this the default policies are enough. So far the only index which actually rolled over, was the only one which grew above a max shard size of 50gb. Based on my understanding normally the indexes should also roll over automatically if the got older than the defined time? The default policy set the time for rollover to warm state after 2 days.

ilm explain shows me this:

GET test-logs-000001/_ilm/explain
{
  "indices" : {
    "test-logs-000001" : {
      "index" : "test-logs-000001",
      "managed" : true,
      "policy" : "30-days-default",
      "lifecycle_date_millis" : 1645108150068,
      "age" : "4.74d",
      "phase" : "hot",
      "phase_time_millis" : 1645108150137,
      "action" : "rollover",
      "action_time_millis" : 1645108150137,
      "step" : "check-rollover-ready",
      "step_time_millis" : 1645108150137,
      "phase_execution" : {
        "policy" : "30-days-default",
        "phase_definition" : {
          "min_age" : "0ms",
          "actions" : {
            "rollover" : {
              "max_primary_shard_size" : "50gb",
              "max_age" : "30d"
            }
          }
        },
        "version" : 1,
        "modified_date_in_millis" : 1639583831614
      }
    }
  }
}

Since phase_time and action_time are equal it should already have rolled over?

Hope you can help me out.

Best Regards.

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