-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
请问有支持sharded pub sub的计划吗? #156
Comments
可以,这几天增加命令 |
v1.1.8 尝试一下吧,记得反馈 |
上述方法,记得都尝试一下后反馈 |
我看到docs里面提到: 请问假如我只提供一个master node 地址,也是可行的吗? |
可行 |
9/6/2023 2:37:16 AM +00:00 有遇到这个问题。 sample test code:
|
Unhandled exception. System.ArgumentOutOfRangeException: Non-negative number required. (Parameter 'maxValue') |
是你的 Random.Shared.Next(400 - 600) 报错? |
await _cli.SPublishAsync("Price", price); FreeRedis.RedisServerException: 'MOVED 7599 127.0.0.1:7001' 这个是expected的吗 |
'MOVED 7599 127.0.0.1:7001' 集群报的错,你那边方便引用源码吗 |
方便进群,加我的QQ,提供一下测试服务器吗 我测一下几个方法。 |
可以 我尽快测一下 (QQ没有了...) |
weinxin: q2881099 |
Sharded Pub/Sub
From Redis 7.0, sharded Pub/Sub is introduced in which shard channels are assigned to slots by the same algorithm used to assign keys to slots. A shard message must be sent to a node that owns the slot the shard channel is hashed to. The cluster makes sure the published shard messages are forwarded to all nodes in the shard, so clients can subscribe to a shard channel by connecting to either the master responsible for the slot, or to any of its replicas. SSUBSCRIBE, SUNSUBSCRIBE and SPUBLISH are used to implement sharded Pub/Sub.
Sharded Pub/Sub helps to scale the usage of Pub/Sub in cluster mode. It restricts the propagation of messages to be within the shard of a cluster. Hence, the amount of data passing through the cluster bus is limited in comparison to global Pub/Sub where each message propagates to each node in the cluster. This allows users to horizontally scale the Pub/Sub usage by adding more shards.
请问有支持此功能的计划吗?
感谢
The text was updated successfully, but these errors were encountered: