Hot/ultrawarm policy

Hi team,

I’m planning to implement hot/ultrawarm setup for the indices using an ISM policy. I see the indices moved to warm state but I not really see the indicies that transitioned to warm data moved to ultrawarm nodes in the AWS elastic search console(still storing in the data nodes). Can someone help me understand this?

ISM policy:

{
“policy”: {
“policy_id”: “ISM_POLICY”,
“description”: “Demonstrate a hot-warm-delete workflow.”,
“last_updated_time”: 1616128162817,
“schema_version”: 1,
“error_notification”: null,
“default_state”: “hot”,
“states”: [
{
“name”: “hot”,
“actions”: ,
“transitions”: [
{
“state_name”: “warm”,
“conditions”: {
“min_index_age”: “1d”
}
}
]
},
{
“name”: “warm”,
“actions”: [
{
“timeout”: “24h”,
“retry”: {
“count”: 5,
“backoff”: “exponential”,
“delay”: “1h”
},
“warm_migration”: {}
}
],
“transitions”: [
{
“state_name”: “delete”,
“conditions”: {
“min_index_age”: “90d”
}
}
]
},
{
“name”: “delete”,
“actions”: [
{
“delete”: {}
}
],
“transitions”:
}
]
}
}

GET _ultrawarm/migration/_status?v returns nothing.

Hi @RGV,

I believe the migration _status API only shows in progress migrations.
You could use GET _cat/indices/_warm to see the indices currently stored in warm tier.
Do they not show up there?

Yeah, you’re right. This is working as expected. Thanks for looking in to this.