Failed to migrate index to cold storage because another index with the same name already exists in cold storage

[techenthusiast (Hemanth Yarramalli)]

Team,

I am getting below issue when i implemented cold storage on an existing Elasticsearch cluster.

Failed to migrate index to cold storage because another index with the same name already exists in cold storage. Need help in getting around and fixing this issue.

Thanks,
Hemanth

[warkolm (Mark Walkom)]

Welcome to our community!

Where are you seeing this? What is the full error?
What does your policy look like?

[techenthusiast (Hemanth Yarramalli)]

Hi Mark, We are trying to implement the cold storage in our ES domain, Earlier we used to have 'hot-warm-delete' policy. We now wanted to implement 'Hot-warm-cold-delete' policy. I am adding the snippet on how the updated ISM policy looks like.

{
    "policy_id": "es-cluster-3-ism",
    "description": "es index hot-warm-cold-delete workflow.",
    "last_updated_time": 1632754240563,
    "schema_version": 1,
    "error_notification": {
        "destination": {
            "slack": {
                "url": "<placeholder>"
            }
        },
        "message_template": {
            "source": "The index {{ctx.index}} failed during policy execution - {{ctx.policy_id}}.",
            "lang": "mustache"
        }
    },
    "default_state": "hot",
    "states": [
        {
            "name": "hot",
            "actions": [],
            "transitions": [
                {
                    "state_name": "warm",
                    "conditions": {
                        "min_index_age": "1h"
                    }
                }
            ]
        },
        {
            "name": "warm",
            "actions": [
                {
                    "retry": {
                        "count": 5,
                        "backoff": "exponential",
                        "delay": "1h"
                    },
                    "warm_migration": {}
                }
            ],
            "transitions": [
                {
                    "state_name": "cold",
                    "conditions": {
                        "min_index_age": "1h"
                    }
                }
            ]
        },
        {
            "name": "cold",
            "actions": [
                {
                    "cold_migration": {
                        "start_time": null,
                        "end_time": null,
                        "timestamp_field": "@timestamp",
                        "ignore": "none"
                    }
                }
            ],
            "transitions": [
                {
                    "state_name": "delete",
                    "conditions": {
                        "min_index_age": "1h"
                    }
                }
            ]
        },
        {
            "name": "delete",
            "actions": [
                {
                    "notification": {
                        "destination": {
                            "slack": {
                                "url": "<placeholder>"
                            }
                        },
                        "message_template": {
                            "source": "The index {{ctx.index}} is being deleted - {{ctx.policy_id}}.",
                            "lang": "mustache"
                        }
                    }
                },
                {
                    "cold_delete": {}
                }
            ],
            "transitions": []
        }
    ],
    "ism_template": [
        {
            "index_patterns": [
                "logstash-*"
            ],
            "priority": 100,
            "last_updated_time": 1632754240562
        }
    ]
}

[warkolm (Mark Walkom)]

Is this is indeed ism then that's an aws concept, it's not something that we can help with sorry.