Hot/ultrawarm policy

Plugins Index Management
,
1

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”:
}
]
}
}

Screen Shot 2021-03-19 at 6.42.31 PM
Screen Shot 2021-03-19 at 6.42.31 PM3064×626 132 KB

GET _ultrawarm/migration/_status?v returns nothing.

2

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?

3

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

4

Hello, I’ve got the same issue. The transition from the Hot to Warm phase doesn’t work for me.
Could you help me?

{
    "id": "opensearch_prod_app_logs_delete_after_90d",
    "seqNo": 50341,
    "primaryTerm": 1,
    "policy": {
        "policy_id": "opensearch_prod_app_logs_delete_after_90d",
        "description": "A policy that changes the replica count between hot and warm states, and delete indexes after 90 days",
        "last_updated_time": 1647604204361,
        "schema_version": 12,
        "error_notification": null,
        "default_state": "hot",
        "states": [
            {
                "name": "hot",
                "actions": [
                    {
                        "replica_count": {
                            "number_of_replicas": 1
                        }
                    }
                ],
                "transitions": [
                    {
                        "state_name": "warm",
                        "conditions": {
                            "min_index_age": "7d"
                        }
                    }
                ]
            },
            {
                "name": "warm",
                "actions": [
                    {
                        "replica_count": {
                            "number_of_replicas": 0
                        }
                    },
                    {
                        "warm_migration": {}
                    }
                ],
                "transitions": [
                    {
                        "state_name": "delete",
                        "conditions": {
                            "min_index_age": "90d"
                        }
                    }
                ]
            },
            {
                "name": "delete",
                "actions": [
                    {
                        "delete": {}
                    }
                ],
                "transitions": []
            }
        ],
        "ism_template": [
            {
                "index_patterns": [
                    "prod-app-*"
                ],
                "priority": 100,
                "last_updated_time": 1647604204361
            }
        ]
    }
}
5

https://opensearch.test.com/_cat/indices/_warm?v
EMPTY

Знімок екрана 2022-03-18 о 13.53.12
Знімок екрана 2022-03-18 о 13.53.121594×534 29.4 KB

6

How to troubleshoot it?

Знімок екрана 2022-03-18 о 13.54.36
Знімок екрана 2022-03-18 о 13.54.362938×380 68.6 KB

7

Was this a separate issue @okapko or the same as discussed over on this thread?

8

Hi, Drew

Yeah, it was the same issue. And it works now thanks to your help.
But now I’ve got a new issue after updating to v1.2.
_hot and _warm indexes are not accessible from API and Dashboards.