Skip to content
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

ILM needs to account for the possibility that removing the retention leases on the leader can fail #39181

Closed
jasontedor opened this issue Feb 20, 2019 · 2 comments · Fixed by #39281

Comments

@jasontedor
Copy link
Member

When ILM is managing a following index, it will attempt to perform an unfollow action on the follower. It can be however that the unfollow action succeeds to make the index into a non-following index, yet the unfollow action completes with an error. This can occur if the follower was not able to remove the retention leases on its leader (e.g., a network connectivity issue). ILM on the following side should accept this possibility and not put the lifecycle into an error state. This can be determined when the unfollow action fails with an ElasticsearchException with the metadata es.failed_to_remove_retention_leases.

Relates #34648
Relates #39088

@jasontedor jasontedor added blocker v7.0.0 :Distributed/CCR Issues around the Cross Cluster State Replication features :Data Management/ILM+SLM Index and Snapshot lifecycle management v6.7.0 v8.0.0 v7.2.0 labels Feb 20, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@danielmitterdorfer danielmitterdorfer added >bug and removed :Distributed/CCR Issues around the Cross Cluster State Replication features labels Feb 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants