[8.0] Clarify unassigned.reason docs (#81017)
#81119
Merged
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
Today we indicate that the `unassigned.reason` field in various APIs indicates the reason why a shard is unassigned. This isn't really true, it tells you some information about the event that caused the shard to _become_ unassigned (or which most recently changed its routing table entry while remaining unassigned) but tells you almost nothing about why the shard _is now_ unassigned and how to fix it. That's what the allocation explain API is for. This commit clarifies this point in the docs. Closes elastic#80892 Co-authored-by: James Rodewig <james.rodewig@elastic.co>
DaveCTurner
added
auto-merge-without-approval
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backports the following commits to 8.0:
unassigned.reasondocs (Clarifyunassigned.reasondocs #81017)