diff options
| author | Harkrishn Patro <30795839+hpatro@users.noreply.github.com> | 2022-01-03 01:54:47 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-02 16:54:47 -0800 |
| commit | 9f8885760b53e6d3952b9c9b41f9e6c48dfa6cec (patch) | |
| tree | 770dfdbff19a1a2a1c71a642ebd844d592ef3d26 /redis.conf | |
| parent | b8ba942ac2aabf51fd96134d9fa21b47d3baff4a (diff) | |
| download | redis-9f8885760b53e6d3952b9c9b41f9e6c48dfa6cec.tar.gz | |
Sharded pubsub implementation (#8621)
This commit implements a sharded pubsub implementation based off of shard channels.
Co-authored-by: Harkrishn Patro <harkrisp@amazon.com>
Co-authored-by: Madelyn Olson <madelyneolson@gmail.com>
Diffstat (limited to 'redis.conf')
| -rw-r--r-- | redis.conf | 9 |
1 files changed, 9 insertions, 0 deletions
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 |