# Datastream Index Rollover issue

**URL:** <https://discuss.elastic.co/t/datastream-index-rollover-issue/378689>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [May 29, 2025, 8:58am UTC](https://discuss.elastic.co/t/datastream-index-rollover-issue/378689 "2025-05-29T08:58:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)\
**Post date:** [May 29, 2025, 8:58am UTC](https://discuss.elastic.co/t/datastream-index-rollover-issue/378689/1 "2025-05-29T08:58:51Z")

</div>

Hi Team,

I have this index as part of datastream which is still in HOT phase , with current step as ERROR

```auto
{
  "failed_step": "update-rollover-lifecycle-date",
  "step_info": {
    "type": "illegal_state_exception",
    "reason": "no rollover info found for [.ds-abc-2025.05.25-000004] with rollover target [traces-abc-maint], the index has not yet rolled over with that target"
  }
}

```

This index do have a policy tagged & the indices are rolled over everyday 1D or 50GB size.

There are new indices created post 25 successfully. This index is stuck.

What actions could be taken so that this follow the policy and moves from HOT Phase to next Phase (WARM node) ?

Thanks

---

<div class="post-metadata">

**Author:** ![NgDinhNamEtiis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ngdinhnametiis/32/135683_2.png) [@NgDinhNamEtiis](https://discuss.elastic.co/u/NgDinhNamEtiis)\
**Post date:** [May 29, 2025, 10:57am UTC](https://discuss.elastic.co/t/datastream-index-rollover-issue/378689/2 "2025-05-29T10:57:13Z")

</div>

**Your situation look like this:**  
[ILM Error: the index has not yet rolled over with that target : r/elasticsearch](https://www.reddit.com/r/elasticsearch/comments/w5bo9p/ilm_error_the_index_has_not_yet_rolled_over_with/)

**The reddit post also link to Elastic Github:**  
[Rollover sometimes does not attach Rollover Info to index metadata · Issue #49413 · elastic/elasticsearch](https://github.com/elastic/elasticsearch/issues/49413)

**In a nutshell:**  
From what I understand your index may or may not have a `RolloverInfo`

and a workaround as well:

```auto
POST _ilm/move/cloudflare-2022.07.14-000001
{
  "current_step": { 
    "phase": "hot",
    "action": "rollover",
    "name": "ERROR"
  },
  "next_step": { 
    "phase": "hot",
    "action": "rollover",
    "name": "set-indexing-complete"
  }
}

```

You should try it, and hope you let me know the result 😁

---

<div class="post-metadata">

**Author:** ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)\
**Post date:** [May 29, 2025, 12:42pm UTC](https://discuss.elastic.co/t/datastream-index-rollover-issue/378689/3 "2025-05-29T12:42:32Z")

</div>

Thanks @NgDinhNamEtiis for sharing the details. I will review and let you know if the issue get fixed.