Rollover Fails of max_size condition


I Am trying to create a ilm policy that rolls over my index on size condition

My ilm policy looks like :

"testing_ilm_dataloss" : {
"version" : 7,
"modified_date" : "2020-08-06T14:25:09.434Z",
"policy" : {
"phases" : {
"hot" : {
"min_age" : "0ms",
"actions" : {
"rollover" : {
"max_size" : "5mb"
"set_priority" : {
"priority" : 100

Rollover works fine on age condition but when I try to rollover only on size I don't see any rollover happening to by index.

But when the data is being loaded to the respective index, rollover doesn't happen on the size given(5mb In this case). Below is the rolled over shard details:

index shard prirep state docs store node

dataloss_monitoring-2020.08.07-1 0 p STARTED 726933 34.8mb svlitctd
dataloss_monitoring-2020.08.07-1 0 r STARTED 726933 35.4mb svlitcid
dataloss_monitoring-2020.08.07-000003 0 p STARTED 1336040 62.6mb svlitctd
dataloss_monitoring-2020.08.07-000003 0 r STARTED 1336040 64.5mb svlitcid
dataloss_monitoring-2020.08.07-000002 0 r STARTED 460131 22.9mb svlitctd
dataloss_monitoring-2020.08.07-000002 0 p STARTED 460131 22.4mb svlitcid

Can you please let me know what should be done to get the rollover function on the exact size condition.


Rollover is checked periodically (every 10 minutes by default if I recall correctly). This is great for production size shards but not necessarily when testing it like you are now. Also be aware that the shard size can grow and shrink as merging occurs, so the size threshold is an estimate.

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