# Index.lifecycle.rollover\_alias does not point to index **URL:** \ **Category:** Elasticsearch\ **Tags:** ilm-index-lifecycle-management\ **Created:** [October 1, 2020, 7:06am UTC](https://discuss.elastic.co/t/index-lifecycle-rollover-alias-does-not-point-to-index/250609 "2020-10-01T07:06:48Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Zoltan\_Kovacs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zoltan_kovacs/32/76500_2.png) [@Zoltan\_Kovacs](https://discuss.elastic.co/u/Zoltan_Kovacs)\ **Post date:** [October 1, 2020, 7:06am UTC](https://discuss.elastic.co/t/index-lifecycle-rollover-alias-does-not-point-to-index/250609/1 "2020-10-01T07:06:48Z")
Hello @warkolm ! I run to this error today. I use NLog to write to ES. I would like to use rollover for not blow up my monthly index more than 50GB. Error: ```auto [2020-10-01T07:54:17,209][ERROR][o.e.x.i.IndexLifecycleRunner] [BTLSRV1] policy [btllogs-ilm-policy] for index [btllogs-system-2020.10] failed on step [{"phase":"hot","action":"rollover","name":"check-rollover-ready"}]. Moving to ERROR step java.lang.IllegalArgumentException: index.lifecycle.rollover_alias [btllogs-ra] does not point to index [btllogs-system-2020.10] at org.elasticsearch.xpack.core.ilm.WaitForRolloverReadyStep.evaluateCondition(WaitForRolloverReadyStep.java:104) [x-pack-core-7.8.0.jar:7.8.0] at org.elasticsearch.xpack.ilm.IndexLifecycleRunner.runPeriodicStep(IndexLifecycleRunner.java:173) [x-pack-ilm-7.8.0.jar:7.8.0] at org.elasticsearch.xpack.ilm.IndexLifecycleService.triggerPolicies(IndexLifecycleService.java:329) [x-pack-ilm-7.8.0.jar:7.8.0] at org.elasticsearch.xpack.ilm.IndexLifecycleService.triggered(IndexLifecycleService.java:267) [x-pack-ilm-7.8.0.jar:7.8.0] at org.elasticsearch.xpack.core.scheduler.SchedulerEngine.notifyListeners(SchedulerEngine.java:183) [x-pack-core-7.8.0.jar:7.8.0] at org.elasticsearch.xpack.core.scheduler.SchedulerEngine$ActiveSchedule.run(SchedulerEngine.java:211) [x-pack-core-7.8.0.jar:7.8.0] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?] at java.lang.Thread.run(Thread.java:832) [?:?] ``` Index Template "btllogs" Settings: ```auto { "index": { "lifecycle": { "name": "btllogs-ilm-policy", "rollover_alias": "btllogs-ra" }, "highlight": { "max_analyzed_offset": "10000000" }, "refresh_interval": "5s", "number_of_shards": "1" } } ``` Policy: ```auto PUT _ilm/policy/btllogs-ilm-policy { "policy": { "phases": { "hot": { "min_age": "0ms", "actions": { "rollover": { "max_age": "31d", "max_size": "50gb" }, "set_priority": { "priority": 100 } } }, "warm": { "actions": { "allocate": { "number_of_replicas": 0, "include": {}, "exclude": {} }, "shrink": { "number_of_shards": 1 }, "forcemerge": { "max_num_segments": 1 }, "set_priority": { "priority": 70 } } }, "cold": { "min_age": "60d", "actions": { "freeze": {}, "allocate": { "number_of_replicas": 0, "include": {}, "exclude": {} }, "set_priority": { "priority": 30 } } }, "delete": { "min_age": "366d", "actions": { "delete": {} } } } } } ``` What am I missing in this case? Thanks a lot. ---
**Author:** ![kavierkoo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kavierkoo/32/86555_2.png) [@kavierkoo](https://discuss.elastic.co/u/kavierkoo)\ **Post date:** [October 1, 2020, 10:01am UTC](https://discuss.elastic.co/t/index-lifecycle-rollover-alias-does-not-point-to-index/250609/2 "2020-10-01T10:01:28Z")
Can you do a `ilm exlpain` on the index to help with the debugging > **[Explain lifecycle API | Elasticsearch Reference \[7.9\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-explain-lifecycle.html)** ---
**Author:** ![Zoltan\_Kovacs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zoltan_kovacs/32/76500_2.png) [@Zoltan\_Kovacs](https://discuss.elastic.co/u/Zoltan_Kovacs)\ **Post date:** [October 1, 2020, 11:05am UTC](https://discuss.elastic.co/t/index-lifecycle-rollover-alias-does-not-point-to-index/250609/3 "2020-10-01T11:05:56Z")
Index Settings (ilm): ```auto "index": { "lifecycle": { "name": "btllogs-ilm-policy", "rollover_alias": "btllogs-ra" }, "highlight": { "max_analyzed_offset": "10000000" }, "refresh_interval": "5s", "number_of_shards": "1", "provided_name": "btllogs-system-2020.10", "creation_date": "1601499626518", "priority": "100", "number_of_replicas": "1", "uuid": "sKdP-sEDQ965HZybNt4tBg", "version": { "created": "7080099" } } ``` ---
**Author:** ![kavierkoo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kavierkoo/32/86555_2.png) [@kavierkoo](https://discuss.elastic.co/u/kavierkoo)\ **Post date:** [October 1, 2020, 11:25am UTC](https://discuss.elastic.co/t/index-lifecycle-rollover-alias-does-not-point-to-index/250609/4 "2020-10-01T11:25:32Z")
You index name seems incorrect for ilm. Usually it end with `xxx-000001` also did you bootstrap your first index? Perhaps you can take a look at link below: > To automate rollover and management of time series indices with ILM using an index alias > **[Tutorial: Automate rollover with ILM | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started-index-lifecycle-management.html#manage-time-series-data-without-data-streams)** Hope this can help you! ---
**Author:** ![Zoltan\_Kovacs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zoltan_kovacs/32/76500_2.png) [@Zoltan\_Kovacs](https://discuss.elastic.co/u/Zoltan_Kovacs)\ **Post date:** [October 12, 2020, 7:24am UTC](https://discuss.elastic.co/t/index-lifecycle-rollover-alias-does-not-point-to-index/250609/5 "2020-10-12T07:24:35Z")
OK. Thank you. I use [date math index name](https://www.elastic.co/guide/en/elasticsearch/reference/7.x/date-math-index-names.html) in the end. It isn't so intuitive... ---
**Author:** ![kavierkoo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kavierkoo/32/86555_2.png) [@kavierkoo](https://discuss.elastic.co/u/kavierkoo)\ **Post date:** [October 12, 2020, 1:26pm UTC](https://discuss.elastic.co/t/index-lifecycle-rollover-alias-does-not-point-to-index/250609/6 "2020-10-12T13:26:18Z")
If you wish to have date in your index name, you could take a read at this ticket. > [@Date in index name doesn't change on rollover on the next day](https://discuss.elastic.co/t/date-in-index-name-doesnt-change-on-rollover-on-the-next-day/226701/4): > > Okay, in that case it looks like the first index was not created with date math, rollover will only perpetuate the date math in the name if the initial index was created with date math (it would be named something like \ if it were created with date math. In order to migrate it, it depends on what version of ES you're running, what version are you using? (Alternatively, if you're just testing, you can start over, but I understand that's not feasible with live data) ---
**Author:** ![Zoltan\_Kovacs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zoltan_kovacs/32/76500_2.png) [@Zoltan\_Kovacs](https://discuss.elastic.co/u/Zoltan_Kovacs)\ **Post date:** [October 13, 2020, 7:51am UTC](https://discuss.elastic.co/t/index-lifecycle-rollover-alias-does-not-point-to-index/250609/7 "2020-10-13T07:51:00Z")
It runs fine in my environment. Thanks for your attention. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 10, 2020, 7:51am UTC](https://discuss.elastic.co/t/index-lifecycle-rollover-alias-does-not-point-to-index/250609/8 "2020-11-10T07:51:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.