# How to manually update policy or proceed in phase

**URL:** <https://discuss.elastic.co/t/how-to-manually-update-policy-or-proceed-in-phase/202622>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [October 8, 2019, 6:56am UTC](https://discuss.elastic.co/t/how-to-manually-update-policy-or-proceed-in-phase/202622 "2019-10-08T06:56:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rmadisonhaynie](https://avatars.discourse-cdn.com/v4/letter/r/e9a140/32.png) [@rmadisonhaynie](https://discuss.elastic.co/u/rmadisonhaynie)\
**Post date:** [October 8, 2019, 6:56am UTC](https://discuss.elastic.co/t/how-to-manually-update-policy-or-proceed-in-phase/202622/1 "2019-10-08T06:56:05Z")

</div>

Hello, I have several times an index will get stuck due to mis-configuration or get an error while testing out the ILM API. I should hopefully get this all resolved but what bothers me is once an index gets stuck like this I don't know how to progress it.

Example:  
I had a policy for warm phase

```
"warm": {
    "min_age": "1d",
    "actions": {
      "readonly" : { },
      "forcemerge": {
        "max_num_segments": 1
      },
      "allocate": {
        "include" : {
          "box_type": "hot,warm"
        }
      }
    }
  }

```

It would get stuck saying "Waiting for [5] shards to be allocated to nodes matching the given filters". Issue is I have no box\_type of hot or warm. So how could I then fix this misconfiguration and continue the ilm? Is it possible to update the executing policy on an index? Or to assign a new policy to index but change it's lifetime?

---

<div class="post-metadata">

**Author:** ![rmadisonhaynie](https://avatars.discourse-cdn.com/v4/letter/r/e9a140/32.png) [@rmadisonhaynie](https://discuss.elastic.co/u/rmadisonhaynie)\
**Post date:** [October 9, 2019, 11:35am UTC](https://discuss.elastic.co/t/how-to-manually-update-policy-or-proceed-in-phase/202622/2 "2019-10-09T11:35:58Z")

</div>

I think my question is largely answered by:

To unblock waiting for allocation issue is to remove the setting on the index itself  
For example, remove from the index setting the follow:  
"index.routing.allocation.include.box\_type": "hot,warm"

---

<div class="post-metadata">

**Author:** ![rmadisonhaynie](https://avatars.discourse-cdn.com/v4/letter/r/e9a140/32.png) [@rmadisonhaynie](https://discuss.elastic.co/u/rmadisonhaynie)\
**Post date:** [October 11, 2019, 11:08am UTC](https://discuss.elastic.co/t/how-to-manually-update-policy-or-proceed-in-phase/202622/3 "2019-10-11T11:08:14Z")

</div>

Also there's an API to manually move index into a new step [https://www.elastic.co/guide/en/elasticsearch/reference/6.8/ilm-move-to-step.html#\_path\_parameters\_16](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/ilm-move-to-step.html#_path_parameters_16)

---

<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:** [November 8, 2019, 11:08am UTC](https://discuss.elastic.co/t/how-to-manually-update-policy-or-proceed-in-phase/202622/4 "2019-11-08T11:08:14Z")

</div>

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