Closed
Description
Description
I'm trying to use sUnsubscribe
in the cluster mode. I find out it supports both string and array. Based on the current implementation, the array type implicitly enforces all the channels to be hashed to the same slot, otherwise an error will throw says ErrorReply: CROSSSLOT Keys in request don't hash to the same slot
.
Just checking is that a intentional design or a bug?
Node.js Version
16
Redis Server Version
No response
Node Redis Version
No response
Platform
No response
Logs
ErrorReply: CROSSSLOT Keys in request don't hash to the same slot