-
Notifications
You must be signed in to change notification settings - Fork 156
Update data-tiers.md #3003
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
Update data-tiers.md #3003
Conversation
The existing description of "automatic data tier migration" did not explicitly call out the impact of setting "migrate": { "enabled": false } without specifying manual allocation rules. The setting alone can prevent data from moving to a data tier while "succeeding" through the ILM "complete" phase.
🔍 Preview links for changed docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚢
Just a couple of small suggestions. Thanks a lot @maggieghamry!
My pleasure @kilfoyle, thanks so much for the amazingly quick review and approval! 🎉 ❤️ |
Hi @maggieghamry! Just checking: Did you mean to close this PR unmerged? If not, we can reopen, apply the suggestions (if you like) and then merge. I just wouldn't want your proposed changes to be lost. |
So sorry @kilfoyle I sure didn't mean to close this 😅. Yes please, let me know if you're able to apply the suggestions and merge or if you would like me to. Thanks again! |
No problem @maggieghamry! I can take it from here (I'll commit the suggestions and merge the PR once the CI checks pass). :-) |
The existing description of "automatic data tier migration" did not explicitly call out the impact of setting "migrate": {
"enabled": false
} without specifying manual allocation rules. The setting alone can prevent data from moving to a data tier while "succeeding" through the ILM "complete" phase.
I am also including an image that may be a useful addition contextually:
