-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Closed
Labels
:Data Management/ILM+SLMDO NOT USE. Use ":StorageEngine/ILM" or ":Distributed Coordination/SLM" instead.DO NOT USE. Use ":StorageEngine/ILM" or ":Distributed Coordination/SLM" instead.>bugTeam:Data Management (obsolete)DO NOT USE. This team no longer exists.DO NOT USE. This team no longer exists.
Description
The ILM create snapshot step can become stuck in an endless loop of snapshot create and delete if the snapshot creates.
This seems to be a result of org.elasticsearch.xpack.ilm.IndexLifecycleRunner#maybeRunAsyncAction always executing the next async step if an async step completes and the org.elasticsearch.xpack.core.ilm.CreateSnapshotStep triggering a delete of any partial snapshot it creates, which then on completion triggers the create step again. This loop is not even broken by stopping ILM completely because there's no ILM execution state check in the loop.
I think this loop should be broken at least if ILM has been stopped. Maybe in addition to that it would make sense to have a maximum retry count here?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Data Management/ILM+SLMDO NOT USE. Use ":StorageEngine/ILM" or ":Distributed Coordination/SLM" instead.DO NOT USE. Use ":StorageEngine/ILM" or ":Distributed Coordination/SLM" instead.>bugTeam:Data Management (obsolete)DO NOT USE. This team no longer exists.DO NOT USE. This team no longer exists.