It is not clear to me why the new index was rolled out.
Here is my policy:
{
"policy": {
"policy_id": "standard_policy",
"description": "Default policy",
"last_updated_time": 1585640752093,
"schema_version": 1,
"error_notification": null,
"default_state": "rollover",
"states": [
{"name": "rollover",
"actions": [
{"retry": {
"count": 20,
"backoff": "constant",
"delay": "1h"},
"rollover": {
"min_size": "25gb",
"min_index_age": "7d"}
}
],
"transitions": [
{"state_name": "search",
"conditions": { "min_index_age": "7d" } },
{"state_name": "search",
"conditions": { "min_size": "23gb"} }
]
},
{"name": "search",
"actions": [
{ "timeout": "24h",
"retry": { "count": 5,
"backoff": "constant",
"delay": "1h" },
"force_merge": {"max_num_segments": 1}}
],
"transitions": [{"state_name": "delete",
"conditions": {"min_index_age": "30d"}}]
},
{ "name": "delete",
"actions": [
{"retry": { "count": 20,
"backoff": "constant",
"delay": "1h"},
"delete": {} }
],
"transitions": []
}
]
} }
So, if I understand correctly the new index should be rolled out only in case of “min_size”: “25gb” or “min_index_age”: “7d”.
But here is what I have right now:
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open aws-logs-000004 wTdOSjH-T7WKDk_gg8Xaxw 3 1 28116489 280742 20gb 10gb
green open aws-logs-000005 TeGlVKXRTj-DDzCq_NxwHA 3 1 9607375 1416 6.6gb 3.3gb
aws-logs-000004 has creation date: “creation_date” : “1585559545398”, which is Monday, 30 March 2020 г., 9:12:25.398. 2 days ago. And it also has a size much smaller than 25Gb.
So the question: is there any way to understand why aws-logs-000005 was rolled out at the time when aws-logs-000004 was not old enough and had size much smaller than a threshold.
