PUBSUB NUMSUB inconsistency in cluster mode

[JrooTJunior]

I'm currently using KeyDB in cluster mode and have encountered an issue with the PUBSUB NUMSUB command. While PUBLISH and SUBSCRIBE commands work correctly in cluster mode, PUBSUB NUMSUB provides inconsistent results depending on which node my service communicating with.

My use case:

• I need to use the PubSub mechanism in cluster mode.
• I use PUBSUB NUMSUB to detect if specified channels are open.

Problem:

The PUBSUB NUMSUB command returns different results based on the node being queried, leading to unreliable channel status information across the cluster.

Context:

I understand that Redis 7 introduced new commands (SPUBLISH, SSUBSCRIBE, PUBSUB SHARDNUMSUB) to address this issue in cluster mode. However, since KeyDB is based on Redis 6, these commands are not available.

Request for assistance:

I'm seeking guidance on how to resolve this issue in KeyDB. Possible solutions I'm considering:

1. Is there a way to modify PUBSUB NUMSUB behavior to provide consistent results across all nodes in the cluster?
2. Could new commands similar to those in Redis 7 be added to KeyDB to handle this situation correctly?
3. Are there any other workarounds or solutions you can suggest for my use case?

Any insights or recommendations would be greatly appreciated. I'm open to exploring different approaches to ensure reliable PubSub functionality in my KeyDB cluster setup.

Thank you for your time and assistance.