New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retrying an ILM action that is an AsyncActionStep does not work due to execution model changes #35397
Labels
Comments
dakrone
added
>bug
blocker
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
labels
Nov 8, 2018
Pinging @elastic/es-core-infra |
This looks very similar to #34618, a similar solution might be applicable. |
talevy
added a commit
to talevy/elasticsearch
that referenced
this issue
Nov 9, 2018
Before, moving to a failed step would only change the step info to be that of the failed step. This means two things. 1. Async Steps would never be triggered to execute 2. If there are inherent problems with the action definition that can be fixed with a policy update, these changes were not being reflected by the new execution info. Changes now 1. Async steps are executed after the move to the failed step in cluster state 2. the lifecycle execution info's phase definition is updated from the current latest policy definition, even though the index isn't moving to a new phase. Closes elastic#35397.
talevy
added a commit
that referenced
this issue
Nov 12, 2018
#35406) Before, moving to a failed step would only change the step info to be that of the failed step. This means two things. 1. Async Steps would never be triggered to execute 2. If there are inherent problems with the action definition that can be fixed with a policy update, these changes were not being reflected by the new execution info. Changes now 1. Async steps are executed after the move to the failed step in cluster state 2. the lifecycle execution info's phase definition is updated from the current latest policy definition, even though the index isn't moving to a new phase. Closes #35397.
talevy
added a commit
that referenced
this issue
Nov 12, 2018
#35406) Before, moving to a failed step would only change the step info to be that of the failed step. This means two things. 1. Async Steps would never be triggered to execute 2. If there are inherent problems with the action definition that can be fixed with a policy update, these changes were not being reflected by the new execution info. Changes now 1. Async steps are executed after the move to the failed step in cluster state 2. the lifecycle execution info's phase definition is updated from the current latest policy definition, even though the index isn't moving to a new phase. Closes #35397.
pgomulka
pushed a commit
to pgomulka/elasticsearch
that referenced
this issue
Nov 21, 2018
elastic#35406) Before, moving to a failed step would only change the step info to be that of the failed step. This means two things. 1. Async Steps would never be triggered to execute 2. If there are inherent problems with the action definition that can be fixed with a policy update, these changes were not being reflected by the new execution info. Changes now 1. Async steps are executed after the move to the failed step in cluster state 2. the lifecycle execution info's phase definition is updated from the current latest policy definition, even though the index isn't moving to a new phase. Closes elastic#35397.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When an index is stuck in the error state of a step which is an
AsyncActionStep
, like so:With error:
When I correct the policy and issue a
POST /foo/_ilm/retry
...The now
warm/shrink/shrink
step never executes, because we only executeAsyncActionStep
s when they are transitioned into.The 'retry' API should perform the correct steps to retry any type of operation.
The text was updated successfully, but these errors were encountered: