Skip to content

Conversation

@dakrone
Copy link
Member

@dakrone dakrone commented Nov 15, 2019

Backports the following commits to 7.5:

When triggered either by becoming master, a new cluster state, or a
periodic schedule, an ILM policy execution through
`maybeRunAsyncAction`, `runPolicyAfterStateChange`, or
`runPeriodicStep` throwing an exception will cause the loop the
terminate. This means that any indices that would have been processed
after the index where the exception was thrown will not be processed by
ILM.

For most execution this is not a problem because the actual running of
steps is protected by a try/catch that moves the index to the ERROR step
in the event of a problem. If an exception occurs prior to step
execution (for example, in fetching and parsing the current
policy/step) however, it causes the loop termination previously
mentioned.

This commit wraps the invocation of the methods specified above in a
try/catch block that provides better logging and does not bubble the
exception up.
@dakrone dakrone added backport :Data Management/ILM+SLM Index and Snapshot lifecycle management v7.5.1 labels Nov 15, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/ILM+SLM)

@dakrone dakrone changed the title [7.5] Don't halt policy execution on policy trigger exception (#49128) [7.5] Don't halt policy execution on policy trigger exception… Nov 15, 2019
@dakrone dakrone merged commit 4432d27 into elastic:7.5 Nov 15, 2019
@dakrone dakrone deleted the backport/7.5/pr-49128 branch November 15, 2019 16:23
@jimczi jimczi added v7.5.0 and removed v7.5.1 labels Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport :Data Management/ILM+SLM Index and Snapshot lifecycle management v7.5.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants