fix(ssubscribe): Force slots refresh on MOVED error when using ssubscribe #1987
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
htemelski-redis
force-pushed
the
ssubscribe_moved
branch
from
59dd4d0 to
8f52163
Compare
htemelski-redis
changed the title
Comment on lines
+77
to
+81
| if (item.command.name == "ssubscribe" && err.message.includes("MOVED")) { | ||
| this.redis.emit("moved"); | ||
| return; | ||
| } | ||
|
|
There was a problem hiding this comment.
Can you please add a comment here explaining how we use the standalone client for ssubscibe connections
There was a problem hiding this comment.
When a hashslot is moved to another shard the message that is sent on the pubsub channel is sunsubscribe, not moved. I suspect this is working because it's caught when the connection is retried. On issuing the ssubscribe command, the response is moved.
elena-kolevska
requested changes
Jun 18, 2025
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.
When issuing a
ssubscribecommand, the Cluster client creates a "regular" Redis client to establish a connection to the correct shard. This doesn't work if there's a failover since the client doesn't know how to correctly handle aMOVEDresponse. This PR handles such events by propagating thessubscribe MOVEDerror from theDataHandler, through theClusterSubscriberand theClusterSubscriberGroupto theRedisClusterclient and forces slots refresh