cluster slots command does not return pfail nodes #10195
Closed
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
Contributor
Contributor
|
I suppose we decided to not add this, let me know if anything changed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
On Tencent Cloud, for a Redis cluster, when readonly is enabled on the slave nodes, we usually use cluster slots to get all the slots information, and then use the slots information to select which slave node to run the command on. However, when the status of the slave node is
fail, we usecluster slotsto select which slave node to run the command on. Therefore, Tencent Cloud introduced thepfailstatus judgment of the slave node to solve the problem of the slave node in thefail?state obtained by the cluster slots command.