是否有一个 golang redis 客户端可以自动检测 pubsub 的新分片？
Is there a golang redis client that auto detects new shards for pubsub?
[更新]：当前redis将每条发布的消息发送到整个集群中的每个节点：
/* -----------------------------------------------------------------------------
* CLUSTER Pub/Sub support
*
* For now we do very little, just propagating PUBLISH messages across the whole
* cluster. In the future we'll try to get smarter and avoiding propagating those
* messages to hosts without receives for a given channel.
* -------------------------------------------------------------------------- */
void clusterPropagatePublish(robj *channel, robj *message) {
clusterSendPublish(NULL, channel, message);
}
此为问题原文，有误：
As I understand it I need to:
Given a channel, find the the node that owns the hash slot.
Subscribe to that node and also to cluster:slots to detect migrations.
Upon slot migration, subscribe to the channel on the new node and keep the old connection open.
Forward messages to the application from the old connection until it closes and remember those messages.
When migration is complete and the old connection closed, forward messages from the new connection, trimming the remembered messages
from the first connection.
Do any of the golang redis client library do this? I’ve looked through
many and it feels like I need to write this logic myself, constantly
polling CLUSTER SLOTS or listening to a pubsub of that info to know
when shards increase or decrease and move my existing pubsub
scriptions from one server to another.
I.e. there lots of golang libs that handle normal GET key with cluster
even if the number of shards changes. But pubsub and cluster is a
whole other thing right?
Redis 集群中的 PubSub 通道在所有节点之间共享 - 消息通过内部总线传递，因此您不需要特殊的客户端 and/or 逻辑。
In a Redis Cluster clients can subscribe to every node, and can also publish to every other node. The cluster will make sure that published messages are forwarded as needed.
[更新]：当前redis将每条发布的消息发送到整个集群中的每个节点：
/* -----------------------------------------------------------------------------
* CLUSTER Pub/Sub support
*
* For now we do very little, just propagating PUBLISH messages across the whole
* cluster. In the future we'll try to get smarter and avoiding propagating those
* messages to hosts without receives for a given channel.
* -------------------------------------------------------------------------- */
void clusterPropagatePublish(robj *channel, robj *message) {
clusterSendPublish(NULL, channel, message);
}
此为问题原文，有误：
As I understand it I need to:
Given a channel, find the the node that owns the hash slot.
Subscribe to that node and also to cluster:slots to detect migrations.
Upon slot migration, subscribe to the channel on the new node and keep the old connection open.
Forward messages to the application from the old connection until it closes and remember those messages.
When migration is complete and the old connection closed, forward messages from the new connection, trimming the remembered messages from the first connection.
Do any of the golang redis client library do this? I’ve looked through many and it feels like I need to write this logic myself, constantly polling
CLUSTER SLOTSor listening to a pubsub of that info to know when shards increase or decrease and move my existing pubsub scriptions from one server to another.I.e. there lots of golang libs that handle normal GET key with cluster even if the number of shards changes. But pubsub and cluster is a whole other thing right?
Redis 集群中的 PubSub 通道在所有节点之间共享 - 消息通过内部总线传递，因此您不需要特殊的客户端 and/or 逻辑。
In a Redis Cluster clients can subscribe to every node, and can also publish to every other node. The cluster will make sure that published messages are forwarded as needed.