update cluster slots reply checking logic for Redis 7 #2108
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
vmihailenco
reviewed
Jun 4, 2022
| @@ -2717,7 +2717,7 @@ func (cmd *ClusterSlotsCmd) readReply(rd *proto.Reader) error { | |||
|
|
|||
| nodes[j].Addr = net.JoinHostPort(ip, port) | |||
|
|
|||
| if n == 3 { | |||
| if n >= 3 { | |||
There was a problem hiding this comment.
If we have 4 replies, then we should also read (and probably discard) the 4th reply as well?
|
Thanks for working on this - I will try to add a build for Redis 7. |
|
Thanks |
evilaffliction
pushed a commit
to reactive-go/redis
that referenced
this pull request
Jun 15, 2022
fix: update cluster slots reply checking logic for redis 7
evilaffliction
pushed a commit
to reactive-go/redis
that referenced
this pull request
Jun 15, 2022
fix: update cluster slots reply checking logic for redis 7
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.
In general a client implementation should just rely on the fact that certain parameters are at fixed positions as specified (referenced from https://redis.io/commands/cluster-slots/)