Nikolay Karadzhov 96d6445d66 fix(ssubscribe): properly resubscribe in case of shard failover (#3098) ...

* fix(ssubscribe): properly resubscribe in case of shard failover

1) when RE failover happens, there is a disconnect
2) affected Client reconnects and tries to resubscribe all existing listeners
ISSUE #1: CROSSSLOT Error - client was doing ssubscribe ch1 ch2.. chN which, after the failover could result in CROSSSLOT ( naturally, becasuse now some slots could be owned by other shards )
FIX: send one ssubscribe command per channel instead of one ssubscribe for all channels
ISSUE #2: MOVED Error - some/all of the channels might be moved somewhere else
FIX: 1: Propagate the error to the Cluster. 2: Cluster rediscovers topology.
3: Cluster resubscribes all listeners of the failed client ( possibly some/all of those will end up in a different client after the rediscovery ) 

fixes: #2902

2025-10-13 11:59:08 +03:00

..

cluster-slots.spec.ts

fix(cluster): prevent infinite loop (#3078)

2025-09-12 14:47:57 +03:00

cluster-slots.ts

fix(ssubscribe): properly resubscribe in case of shard failover (#3098)

2025-10-13 11:59:08 +03:00

index.spec.ts

feat: add cluster/node events (#1855) (#3083)

2025-10-09 16:06:57 +03:00

index.ts

fix(ssubscribe): properly resubscribe in case of shard failover (#3098)

2025-10-13 11:59:08 +03:00

multi-command.ts

new "transform arguments" API for better key and metadata extraction (#2733)

2024-10-31 12:16:59 -04:00