# Change ILM policy

**URL:** <https://discuss.elastic.co/t/change-ilm-policy/269105>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [April 2, 2021, 12:49pm UTC](https://discuss.elastic.co/t/change-ilm-policy/269105 "2021-04-02T12:49:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheHunter1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thehunter1/32/80190_2.png) [@TheHunter1](https://discuss.elastic.co/u/TheHunter1)\
**Post date:** [April 2, 2021, 12:49pm UTC](https://discuss.elastic.co/t/change-ilm-policy/269105/1 "2021-04-02T12:49:17Z")

</div>

Hello,

I have a cluster of 2 nodes HOT and 1 DATA warm,  
and my ILM configuration is set to 1 shard and 1 replica

I checked today my indexes and I found out that My HOT data node is going to hit 90% of DISK, and after investgation I Think if I understand well it's because the one of replica or shar pass to the warm node, but the other can't go anywhere as I have just 1 DATA node.

I would like to know if this way of thinking is correcte, and in this case if I configure ILM like that by making in WARM phase 0 replica, if it will solve the problem, and if I will not have errors after editing it, as packetbeat is already sending data, or should I stop packetbeat before editing the ILM policy

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/5/059a2a840ce5a9132f49edd2c52cfb1eaea4a48c.png)

Hope I explain well my problem  
Thanks for your answers

---

<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:** [April 30, 2021, 12:50pm UTC](https://discuss.elastic.co/t/change-ilm-policy/269105/2 "2021-04-30T12:50:02Z")

</div>

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