-
Notifications
You must be signed in to change notification settings - Fork 525
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
Remove warm phase from default ILM policy #6322
Conversation
@bmorelli25 FYI there are a few minor docs updates here. |
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
|
(cherry picked from commit c3d27d4) # Conflicts: # changelogs/head.asciidoc
* Remove warm phase from default ILM policy (#6322) (cherry picked from commit c3d27d4) # Conflicts: # changelogs/head.asciidoc * Delete head.asciidoc Co-authored-by: Andrew Wilkins <[email protected]>
This pull request does not have a backport label. Could you fix it @axw? 🙏
NOTE: |
Verified using GET _ilm/policy/apm-rollover-30-days
{
"policy": {
"phases": {
"hot": {
"min_age": "0ms",
"actions": {
"rollover": {
"max_size": "50gb",
"max_age": "30d"
},
"set_priority": {
"priority": 100
}
}
}
}
}
} |
Motivation/summary
Remove warm phase from default ILM policy for standalone. Having a warm phase by default causes warm data nodes to spin up after 30 days when autoscaling is enabled; this is surprising to users, and was unintended.
This does not affect existing deployments unless they explicitly opt into overwriting the ILM policy during server initialisation/setup. Users who wish to have a warm phase and have enabled overwriting will need to customise their ILM policy in
apm-server.yml
.Checklist
How to test these changes
Related issues
Closes #6170