# Forcing ILM policy causing cluster to go RED

**URL:** <https://discuss.elastic.co/t/forcing-ilm-policy-causing-cluster-to-go-red/253687>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [October 29, 2020, 12:03pm UTC](https://discuss.elastic.co/t/forcing-ilm-policy-causing-cluster-to-go-red/253687 "2020-10-29T12:03:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Divit\_Sharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/divit_sharma/32/32348_2.png) [@Divit\_Sharma](https://discuss.elastic.co/u/Divit_Sharma)\
**Post date:** [October 29, 2020, 12:03pm UTC](https://discuss.elastic.co/t/forcing-ilm-policy-causing-cluster-to-go-red/253687/1 "2020-10-29T12:03:49Z")

</div>

I am using settings API to force the ILM policy to all my older indices around 4000k. When I run it, my cluster goes into Red state. I don't know why this would be. Any idea?

We have 9 data nodes, 2 client nodes and 3 master.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 3, 2020, 12:10am UTC](https://discuss.elastic.co/t/forcing-ilm-policy-causing-cluster-to-go-red/253687/2 "2020-11-03T00:10:03Z")

</div>

What do the master logs show when this happens?

---

<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:** [December 1, 2020, 12:10am UTC](https://discuss.elastic.co/t/forcing-ilm-policy-causing-cluster-to-go-red/253687/3 "2020-12-01T00:10:06Z")

</div>

Closed on December 1, 2020, 12:10am UTC

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