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

[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

[leibale]

S[UN]SUBSCRIBE behaves just like any other command, either use "hash tags" or call SSUBSCRIBE twice:

// make sure both channels are in the same slots using "hash tags"
await cluster.SSUBSCRIBE(['{tag}1', '{tag}2'], (message, channel) => {
  console.log(message, channel);
});

// SSBUCRIBE twice, once for each slot
await Promise.all([
  cluster.SSUBSCRIBE('1', (message, channel) => {
    console.log(message, channel);
  }),
  cluster.SSUBSCRIBE('2', (message, channel) => {
    console.log(message, channel);
  })
]);

[ngot]

Thanks @leibale . This finding originnates from socketio/socket.io-redis-adapter#500

I believe this is not bug in node-redis. I will close it.