# ILM Policy getting stuck here

**URL:** https://discuss.elastic.co/t/ilm-policy-getting-stuck-here/337383
**Category:** Elasticsearch
**Tags:** ilm-index-lifecycle-management
**Created:** [July 2, 2023, 1:12am UTC](https://discuss.elastic.co/t/ilm-policy-getting-stuck-here/337383 "2023-07-02T01:12:36Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![dhawal](https://avatars.discourse-cdn.com/v4/letter/d/7c8e57/32.png) [@dhawal](https://discuss.elastic.co/u/dhawal)
#### Post date: [July 2, 2023, 1:12am UTC](https://discuss.elastic.co/t/ilm-policy-getting-stuck-here/337383/1 "2023-07-02T01:12:36Z")

</div>

I am getting below mentioned status here for most of the index i have.

[Index name]lifecycle action [migrate] waiting for [6] shards to be moved to the [data\_warm] tier (tier migration preference configuration is [data\_warm, data\_hot])

Please guide how can this be fixed.

```auto
"policy": {
      "phases": {
        "delete": {
          "min_age": "15d",
          "actions": {
            "delete": {
              "delete_searchable_snapshot": true
            }
          }
        },
        "warm": {
          "min_age": "0d",
          "actions": {
            "forcemerge": {
              "max_num_segments": 1
            },
            "readonly": {},
            "set_priority": {
              "priority": 50
            }
          }
        },
        "hot": {
          "min_age": "0ms",
          "actions": {
            "rollover": {
              "max_primary_shard_size": "50gb",
              "max_age": "5d"
            }
          }
        }
      }
    }

```

---

<div class="post-metadata">

### Author: ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)
#### Post date: [July 3, 2023, 10:16am UTC](https://discuss.elastic.co/t/ilm-policy-getting-stuck-here/337383/2 "2023-07-03T10:16:56Z")

</div>

Hi @dhawal,

Welcome to the community. Some more information on the state of your policy and cluster would be useful to help.

Can you check the output of [`ilm/explain`](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-explain-lifecycle.html) and [`cluster/health`](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-health.html) API endpoints? What is the status of your cluster at the moment?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 31, 2023, 10:17am UTC](https://discuss.elastic.co/t/ilm-policy-getting-stuck-here/337383/3 "2023-07-31T10:17:22Z")

</div>

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