From 9f8885760b53e6d3952b9c9b41f9e6c48dfa6cec Mon Sep 17 00:00:00 2001 From: Harkrishn Patro <30795839+hpatro@users.noreply.github.com> Date: Mon, 3 Jan 2022 01:54:47 +0100 Subject: Sharded pubsub implementation (#8621) This commit implements a sharded pubsub implementation based off of shard channels. Co-authored-by: Harkrishn Patro Co-authored-by: Madelyn Olson --- redis.conf | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'redis.conf') diff --git a/redis.conf b/redis.conf index 7289277cf..8804aac37 100644 --- a/redis.conf +++ b/redis.conf @@ -1613,6 +1613,15 @@ lua-time-limit 5000 # # cluster-allow-reads-when-down no +# This option, when set to yes, allows nodes to serve pubsub shard traffic while the +# the cluster is in a down state, as long as it believes it owns the slots. +# +# This is useful if the application would like to use the pubsub feature even when +# the cluster global stable state is not OK. If the application wants to make sure only +# one shard is serving a given channel, this feature should be kept as yes. +# +# cluster-allow-pubsubshard-when-down yes + # Cluster link send buffer limit is the limit on the memory usage of an individual # cluster bus link's send buffer in bytes. Cluster links would be freed if they exceed # this limit. This is to primarily prevent send buffers from growing unbounded on links -- cgit v1.2.1