Fix message for stalled shutdown #89267
Merged
Conversation
This file contains 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
DaveCTurner
added
backport
:Core/Infra/Node Lifecycle
DaveCTurner
force-pushed
the
2022-08-11-backport-89254-7.17
branch
from
6d67d0a to
8e7a16a
Compare
Today if a node shutdown is stalled due to unmoveable shards then we say to use the allocation explain API to find details. In fact, since elastic#78727 we include the allocation explanation in the response already so we should tell users just to look at that instead. This commit adjusts the message to address this. Backport of elastic#89254
DaveCTurner
force-pushed
the
2022-08-11-backport-89254-7.17
branch
from
8e7a16a to
abbf511
Compare
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.
Today if a node shutdown is stalled due to unmoveable shards then we say
to use the allocation explain API to find details. In fact, since #78727
we include the allocation explanation in the response already so we
should tell users just to look at that instead. This commit adjusts the
message to address this.
Backport of #89254