Index state management policy (hot to warm) not working

Plugins Index Management
1

Hi team,

Im using AWS managed ES and Kibana. Im trying to set a policy to automatically move all the indices from hot to warm after 30 days. However Im trying to test keeping the min_index_age as 5m. Once I apply the policy, it says “Successfully initialized policy: uat_32d_policy” however the policy state remains in hot even after an hour which should ideally be changed to warm after 5 minutes.

Pls note I have multiple indices starting with cwl-uat-****** and I have defined the index pattern as “cwl-uat*” in my query.

Can someone pls help or let me know if I have done anything wrong in my query

2

{
“policy_id”: “uat_32d_policy”,
“description”: “uat-hot-warm”,
“last_updated_time”: 1630900263392,
“schema_version”: 1,
“error_notification”: null,
“default_state”: “hot_state”,
“states”: [
{
“name”: “hot_state”,
“actions”: ,
“transitions”: [
{
“state_name”: “warm_state”,
“conditions”: {
“min_index_age”: “5m”
}
}
]
},
{
“name”: “warm_state”,
“actions”: [
{
“timeout”: “2m”,
“retry”: {
“count”: 5,
“backoff”: “exponential”,
“delay”: “2m”
},
“warm_migration”: {}
}
],
“transitions”:
}
],
“ism_template”: [
{
“index_patterns”: [
“cwl-uat-*”
],
“priority”: 100,
“last_updated_time”: 1630690085133
}
]
}

3

smp
smp286×578 23.4 KB

These are the indices im trying to move. Am I supposed to mentioned each index name in the ISM template while creating the policy ??

4

Hi @shaimoh,

Would you try using a schedule more than 5 min ? Try with 30 min …
Because 5 min is the default job interval :

And also make sure that you have “hot” and “cold” attributes on your nodes and you have configured allocations: Policies - OpenSearch documentation

5

Hi,

Thanks for replying

Issue seems to be fixed after extending the timeout period

“state_name”: “warm_state”,
“conditions”: {
“min_index_age”: “32d”
}
}
]
},
{
“name”: “warm_state”,
“actions”: [
{
“timeout”: “24h”,
“retry”: {
“count”: 5,
“backoff”: “exponential”,
“delay”: “1h”