How to fix Index Lifecycle Rollover Alias is empty or not defined

[stephenb (Stephen Brown)]

Well first your max age for rollover is 30d so and currently the index is only 3+ days old and it is not 50 GB shards

@roman-tasi

hot" : {
          "min_age" : "0ms",
          "actions" : {
            "set_priority" : {
              "priority" : 100
            },
            "rollover" : {
              "max_primary_shard_size" : "50gb",
              "max_age" : "30d" < HERE
            }
          }
        },

So the index will not rollover until 50GB or 30d days.

Then really important the next phases are calculated from rollover

So right now your policy says cold 20h after rollover

Then delete 2 days after rollover

And your index has not even rolled over yet... Because it is not 50gb shard or 30 days old

So everything is working as expect but your policy is not right... You need to set the rollover properly...

Read this here

Why don't you just set rollover to 1 day max the delete at 3 days ... Not sure what cold is doing for you....

Update the policy

Force rollover and it should start working

You can force rollover with

POST os-linux/_rollover