Expected Behavior:
As per Redis documentation, Every node of a Redis cluster generates events about its own subset of the keyspace, However, unlike regular Pub/Sub communication in a cluster, events' notifications are not broadcasted to all nodes. keyspace events are node-specific. This means that to receive all keyspace events of a cluster, clients need to subscribe to each of the nodes.
https://redis.io/topics/notificationsCurrent Behavior:
aioredis-cluster lib has provided "psubscribe(self, pattern, *patterns)" to subscribe to patterns but this method subscribe to only one of the master node in cluster.
Question:Any recommended way to subscribe to all nodes of cluster to receive all keyspace events with the APIs supported by aioredis-cluster.
Or
Is there any way of subscribing dynamically to slave node turn into master in case of fail over (master brought down)?
Expected Behavior: As per Redis documentation, Every node of a Redis cluster generates events about its own subset of the keyspace, However, unlike regular Pub/Sub communication in a cluster, events' notifications are not broadcasted to all nodes. keyspace events are node-specific. This means that to receive all keyspace events of a cluster, clients need to subscribe to each of the nodes. https://redis.io/topics/notifications Current Behavior: aioredis-cluster lib has provided "psubscribe(self, pattern, *patterns)" to subscribe to patterns but this method subscribe to only one of the master node in cluster. Question: Any recommended way to subscribe to all nodes of cluster to receive all keyspace events with the APIs supported by aioredis-cluster.
Or Is there any way of subscribing dynamically to slave node turn into master in case of fail over (master brought down)?
Expected Behavior: