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] Add forcemerge action to hot phase with a rollover enabled #77193

Merged
merged 3 commits into from
Sep 15, 2020

Conversation

yuliacech
Copy link
Contributor

@yuliacech yuliacech commented Sep 10, 2020

Summary

Fixes #57642.
This PR adds a forcemerge action to hot phase of index lifecycle policy when rollover is enabled. Forcemerge is now a separate component, that can be re-used in hot and warm phases.

Screenshot

Screenshot 2020-09-10 at 17 18 51

TODO

Add codec option to forcemerge.

@yuliacech yuliacech marked this pull request as ready for review September 10, 2020 15:40
@yuliacech yuliacech requested a review from a team as a code owner September 10, 2020 15:40
@yuliacech yuliacech added Feature:ILM release_note:enhancement Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more v7.10.0 v8.0.0 labels Sep 10, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

@yuliacech
Copy link
Contributor Author

@elasticmachine merge upstream

Copy link
Contributor

@jloleysens jloleysens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work @yuliacech !

Tested locally and the changes are working as expected. I left some comments about how I think we can simplify typing and I would like to get your thoughts on these but do not view them as blocking for this work.

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Build metrics

@kbn/optimizer bundle module count

id value diff baseline
indexLifecycleManagement 73 +1 72

async chunks size

id value diff baseline
indexLifecycleManagement 186.6KB +1.2KB 185.4KB

page load bundle size

id value diff baseline
indexLifecycleManagement 232.4KB +54.0B 232.3KB

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@yuliacech yuliacech merged commit 34238e5 into elastic:master Sep 15, 2020
yuliacech added a commit to yuliacech/kibana that referenced this pull request Sep 15, 2020
…stic#77193)

* [ILM] Add forcemerge action to hot phase with a rollover enabled

* [ILM] Add PR suggestions

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
yuliacech added a commit that referenced this pull request Sep 15, 2020
) (#77501)

* [ILM] Add forcemerge action to hot phase with a rollover enabled

* [ILM] Add PR suggestions

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
@yuliacech yuliacech deleted the ilm_forcemerge branch October 7, 2020 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:ILM release_note:enhancement Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more v7.10.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for forcemerge action in ILM policy hot phase
4 participants