Skip to content

[7.x] Allow forcemerge in the hot phase for ILM policies (#52073) #52083

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

Merged
merged 1 commit into from
Feb 10, 2020

Conversation

dakrone
Copy link
Member

@dakrone dakrone commented Feb 7, 2020

Backports the following commits to 7.x:

* Allow forcemerge in the hot phase for ILM policies

This commit changes the `forcemerge` action to also be allowed in the `hot` phase for policies. The
forcemerge will occur after a rollover, and allows users to take advantage of higher disk speeds for
performing the force merge (on a separate node type, for example).

On caveat with this is that a `forcemerge` in the `hot` phase *MUST* be accompanied by a `rollover`
action. ILM validates policies to ensure this is the case.

Resolves elastic#43165

* Use anyMatch instead of findAny in validation

* Make randomTimeseriesLifecyclePolicy single-pass
@dakrone dakrone added backport :Data Management/ILM+SLM Index and Snapshot lifecycle management v7.7.0 labels Feb 7, 2020
@elasticmachine
Copy link
Collaborator

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

@dakrone dakrone merged commit 37a2e9b into elastic:7.x Feb 10, 2020
@dakrone dakrone deleted the backport/7.x/pr-52073 branch February 10, 2020 15:54
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.7.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants