# Indices not rolling over

**URL:** <https://discuss.elastic.co/t/indices-not-rolling-over/275640>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [June 11, 2021, 4:11am UTC](https://discuss.elastic.co/t/indices-not-rolling-over/275640 "2021-06-11T04:11:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lchan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lchan/32/90857_2.png) [@lchan](https://discuss.elastic.co/u/lchan)\
**Post date:** [June 11, 2021, 4:11am UTC](https://discuss.elastic.co/t/indices-not-rolling-over/275640/1 "2021-06-11T04:11:13Z")

</div>

I am troubleshooting an issue where my indices (filebeats\*) are not rolling from hot to warm.

I changed rollover max\_age=30d to max\_age=1d. However, the indices of the ILM action is "completed" and looks like they won't get rolled over.

1. What is the next troubleshooting step if the ILM policy is setup correctly but still not rolling over?
2. Is there an API to rollover an index manually? I have attached a screen of the warm node setup.

```auto
GET filebeat-7.12.1-2021.06.07-000005/_ilm/explain
{
"indices" : {
"filebeat-7.12.1-2021.06.07-000005" : {
"index" : "filebeat-7.12.1-2021.06.07-000005",
"managed" : true,
"policy" : "filebeat",
"lifecycle_date_millis" : 1623243828019,
"age" : "15.17m",
"phase" : "hot",
"phase_time_millis" : 1623059628176,
"action" : "complete",
"action_time_millis" : 1623243829088,
"step" : "complete",
"step_time_millis" : 1623243829088,
"phase_execution" : {
"policy" : "filebeat",
"phase_definition" : {
"min_age" : "0ms",
"actions" : {
"rollover" : {
"max_size" : "40gb",
"max_age" : "1d"
}
}
},
"version" : 6,
"modified_date_in_millis" : 1623243785876
}
}
}
}

GET _ilm/policy/filebeat
{
"filebeat" : {
"version" : 6,
"modified_date" : "2021-06-09T13:03:05.876Z",
"policy" : {
"phases" : {
"warm" : {
"min_age" : "7d",
"actions" : {
"set_priority" : {
"priority" : 50
}
}
},
"hot" : {
"min_age" : "0ms",
"actions" : {
"rollover" : {
"max_size" : "40gb",
"max_age" : "1d"
}
}
},
"delete" : {
"min_age" : "7d",
"actions" : {
"delete" : {
"delete_searchable_snapshot" : true
}
}
}
}
}
}
}

```

---

<div class="post-metadata">

**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\
**Post date:** [June 11, 2021, 6:10am UTC](https://discuss.elastic.co/t/indices-not-rolling-over/275640/2 "2021-06-11T06:10:40Z")

</div>

Hi,

Are you sure that your index did not rollover? Is there no index filebeat-7.12.1-\*-000006 available?

It is possible that the index did rollover and is still in hot state as your ILM policy defines that an index should switch to warm state 7 days after rollover which would be next week.

There is a manual rollover API: [Rollover API | Elasticsearch Guide [master] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/master/indices-rollover-index.html)

You could try `POST filebeat-7.12.1/_rollover` where `filebeat-7.12.1` is your rollover alias.

Best regards  
Wolfram

---

<div class="post-metadata">

**Author:** ![lchan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lchan/32/90857_2.png) [@lchan](https://discuss.elastic.co/u/lchan)\
**Post date:** [June 12, 2021, 4:55am UTC](https://discuss.elastic.co/t/indices-not-rolling-over/275640/3 "2021-06-12T04:55:14Z")

</div>

@Wolfram_Haussig

That's the issue, the min\_age should have set to 1d. Thanks!

> [@lchan](#):
>
> `min_age`

---

<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:** [July 10, 2021, 4:55am UTC](https://discuss.elastic.co/t/indices-not-rolling-over/275640/4 "2021-07-10T04:55:27Z")

</div>

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