Skip to content

sUnsubscribe throw CROSSSLOT Keys in request don't hash to the same slot #2502

Closed
@ngot

Description

@ngot

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?

https://github.com/redis/node-redis/blob/master/packages/client/lib/cluster/index.ts#LL372C10-L372C10

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions