I have an ILM policy with both max_age
and max_size
specified. Rollover happens as expected about ten minutes after max_age
, but does not seem to happen on max_size
. With max_size
set to 10MB I've seen shard sizes up to 40MB or so. With max_size
set to 100MB I've seen the shard size up to 140MB. In all cases max_age
then appeared to trigger the rollover (or I restarted the test for some other reason).
Does max_size
work? What do I have to do to make it work?
Just in case I have a syntax or typing error I've failed to notice, the policy, from GET _ilm/policy
, is
"filebeat-ilm-policy" : {
"version" : 1,
"modified_date" : "2021-10-29T12:39:06.939Z",
"policy" : {
"phases" : {
"hot" : {
"min_age" : "0ms",
"actions" : {
"rollover" : {
"max_size" : "100mb",
"max_age" : "1d"
},
"set_priority" : {
"priority" : 100
}
}
},
"delete" : {
"min_age" : "7d",
"actions" : {
"delete" : {
"delete_searchable_snapshot" : true
}
}
}
}
}
}