Hello,
I have isssue with rollover error during step with ILM.
I created ILM (all rollover settings disabled) to remove indexes after 365 days.
During ILM work I founded below error:
>
> "step": "check-rollover-ready",
> "previous_step_info": {
> "type": "illegal_argument_exception",
> "reason": "index.lifecycle.rollover_alias [robot-*] does not point to index [robot-2021.01.26]"
When after suggestion I removed rollover alias:
PUT test-2021.01/_settings { "index.lifecycle.rollover_alias": null }
I have error message:
> "previous_step_info": {
> "type": "illegal_argument_exception",
> "reason": "setting [index.lifecycle.rollover_alias] for index [test-2021.05] is empty or not defined"
Hey, I’ve run into this before — it’s definitely confusing.
The issue is that ILM still tries to do the rollover, even if you don’t want it to. Just removing the rollover_alias isn’t enough, because the index gets stuck in the rollover check step.
What works: besides removing the alias, you need to tell ILM to skip that step and go straight to the delete phase.
Yes, exactly — if your index was created from a template that includes index.lifecycle.rollover_alias, it’ll keep applying that setting. That clears the alias just for that index. If you want to prevent this from happening with future indices, you’ll need to remove index.lifecycle.rollover_alias from the index template too.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.