Lifecycle action [migrate] waiting for [1] shards to be moved to the [data_warm] tier (tier migration preference configuration is [data_warm, data_hot])

Elastic Stack Elasticsearch
1

I have set ILM policy as


{
    "aggregations-lifecycle-policy":{
        "version":2,
        "modified_date":"2023-01-25T08:51:42.054Z",
        "policy":{
            "phases":{
                "warm":{
                    "min_age":"10m",
                    "actions":{
                        "set_priority":{
                            "priority":50
                            }
                            }
                            },
                            "cold":{
                                "min_age":"15m",
                                "actions":{
                                    "set_priority":{
                                        "priority":0
                                        }
                                        }
                                        },
                                        "hot":{
                                            "min_age":"0ms",
                                            "actions":{
                                                "set_priority":{
                                                    "priority":100
                                                    },
                                                    "rollover":{
                                                        "max_age":"5m"
                                                        }
                                                        }
                                                        },
                                                        "delete":{
                                                            "min_age":"20m",
                                                            "actions":{
                                                                "delete":{
                                                                    "delete_searchable_snapshot":true
                                                                    }
                                                                    }
                                                                    }
                                                                    }
                                                                    },
                                                                    "in_use_by":{
                                                                        "indices":["aggregation-logs-2023.01.25-000011","aggregation-logs-2023.01.25-000010","aggregation-logs-2023.01.25-000013","aggregation-logs-2023.01.25-000012","aggregation-logs-2023.01.25-000015","aggregation-logs-2023.01.25-000004","aggregation-logs-2023.01.25-000014","aggregation-logs-2023.01.25-000003","aggregation-logs-2023.01.25-000006","aggregation-logs-2023.01.25-000005","aggregation-logs-2023.01.25-000016","aggregation-logs-2023.01.25-000008","aggregation-logs-2023.01.25-000007","aggregation-logs-2023.01.25-000009"],"data_streams":[],"composable_templates":["aggregations-index-template"]}}}

But i see the index is in warm phase only. This is the action status i am seeing.

[aggregation-logs-2023.01.25-000003] lifecycle action [migrate] waiting for [1] shards to be moved to the [data_warm] tier (tier migration preference configuration is [data_warm, data_hot])

I have all 3 nodes

curl -XGET -u un:pass 'http://x.x.62.242:9200/_cat/nodes'
x.x.63.228 50 69  0 0.18 0.09 0.02 w    - ip-x-x-63-228
x.x.62.120 58 61  0 0.00 0.01 0.00 c    - ip-x-x-62-120
x.x.62.242 27 95 21 1.58 2.00 1.95 hims * ip-x-x-62-242
2

Able to fix this by setting number of replicas to 0. But if i wanted to migrate to production what all the things that i have take consideration into?

3

Some of your policy times are way too low for Elasticsearch to work with there, you are better off using larger times even if just testing.

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.