Unnecessary psubscribe Operations in Namespaces Without Local Clients Increasing Redis Pub/Sub Channels about socket.io-redis-adapter HOT 2 CLOSED

@LokeshDaga hi! Did you find the culprit? Is there something we could fix on our end?

from socket.io-redis-adapter.

@darrachequesne This issue we've encountered while using the Redis adapter with our Node.js cluster. This problem arises when there are no clients connected to a particular node, and that node needs to publish a message on a specific namespace.

In this scenario, the node initiates a psubscribe or subscribe action on that namespace. However, since no clients are connected to it, these subscriptions are not removed after the operation is completed. Consequently, this leads to an accumulation of pub-sub channels in the Redis instance, which can impact performance and scalability over time.

Also we are trying to use sharded redis adapter with mode and analysing the performance improvement by using it. But in both scenario number of channels in redis will increase

from socket.io-redis-adapter.