[DOCS] Note index rollover is not automatically monitored #40464
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jrodewig
added
>docs
Collaborator
|
Pinging @elastic/es-core-features |
Contributor
|
If users are looking for a way to automatically roll over when these conditions are met, we do provide that in Basic+ license levels via ILM, so we might want to point users that way. |
Contributor
Author
|
Great point @gwbrown. Pushed a new commit to direct users to ILM for automatic rollovers. |
Contributor
Author
|
Chatted with @Erni who gave a 👍. Will merge now. |
jrodewig
added a commit
that referenced
this pull request
Apr 3, 2019
jrodewig
added a commit
that referenced
this pull request
Apr 3, 2019
gurkankaymak
pushed a commit
to gurkankaymak/elasticsearch
that referenced
this pull request
May 27, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR specifies that the rollover index API only checks for met conditions at the time of the API call only.
Previously, users might assume Elasticsearch would continue monitoring for met conditions after the call.
Resolves #35624.