# Map index to a new ILM

**URL:** <https://discuss.elastic.co/t/map-index-to-a-new-ilm/375056>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [February 26, 2025, 7:30am UTC](https://discuss.elastic.co/t/map-index-to-a-new-ilm/375056 "2025-02-26T07:30:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chaviru](https://avatars.discourse-cdn.com/v4/letter/c/59ef9b/32.png) [@Chaviru](https://discuss.elastic.co/u/Chaviru)\
**Post date:** [February 26, 2025, 7:30am UTC](https://discuss.elastic.co/t/map-index-to-a-new-ilm/375056/1 "2025-02-26T07:30:57Z")

</div>

Hello guys,

I have a usecase where I need to map my current index to a new ILM policy. So I created a new ILM polciy with my requirement and then deleted the existing ILM for the index and then added the new ILM for this index. But when I do this the index health turned to yellow. And I tried to rollover the index and then a new index was created but the data is not ingested to this new index. The rollover is not happening correctly. My current index is filled with more than 50GB. But not rollovering.

---

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [February 26, 2025, 9:32am UTC](https://discuss.elastic.co/t/map-index-to-a-new-ilm/375056/2 "2025-02-26T09:32:04Z")

</div>

Welcome back to the forum.

it will likely help to see the new ILM policy

And the setting for the index which is now yellow, i.e.

GET /yellow-index-name/\_settings

Usually an index is yellow as shards are not allocated, did you change anything with respect to the number of shards or replicas from "old"ILM to "new" ILM ?

You can easily see if you have unallocated shards with:

GET \_cluster/health

---

<div class="post-metadata">

**Author:** ![Chaviru](https://avatars.discourse-cdn.com/v4/letter/c/59ef9b/32.png) [@Chaviru](https://discuss.elastic.co/u/Chaviru)\
**Post date:** [February 26, 2025, 9:53am UTC](https://discuss.elastic.co/t/map-index-to-a-new-ilm/375056/3 "2025-02-26T09:53:22Z")

</div>

Thank you for the quick response. I restarted the deployment as the deployment was down due to too many requests. And it is restarting now for many hours and the following errors are showing.

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

I tried to restore data from a older snapshot and it is giving me an error that index is already existing.

---

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [February 26, 2025, 10:28am UTC](https://discuss.elastic.co/t/map-index-to-a-new-ilm/375056/4 "2025-02-26T10:28:37Z")

</div>

> [@Chaviru](#):
>
> I tried to restore data from a older snapshot and it is giving me an error that index is already existing.

Yes, you cannot restore over an existing index. There is rename on restore

> **[Restore a snapshot | Elasticsearch Guide \[8.17\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-restore-snapshot.html#rename-on-restore)**

but ... I think you have more serious issues.

Are you a paying custome? If so I would strongly suggest to open a support case.