Update redis conf (#8707)

* Fix typo for compatible
* Trim trailing whitespace
This commit is contained in:
Javier Li Sam 2021-04-21 03:51:52 -07:00 committed by GitHub
parent ac36161694
commit b9d7d55b2c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -148,7 +148,7 @@ tcp-keepalive 300
# server to connected clients, masters or cluster peers. These files should be # server to connected clients, masters or cluster peers. These files should be
# PEM formatted. # PEM formatted.
# #
# tls-cert-file redis.crt # tls-cert-file redis.crt
# tls-key-file redis.key # tls-key-file redis.key
# #
# If the key file is encrypted using a passphrase, it can be included here # If the key file is encrypted using a passphrase, it can be included here
@ -872,8 +872,8 @@ replica-priority 100
# ACL LOG # ACL LOG
# #
# The ACL Log tracks failed commands and authentication events associated # The ACL Log tracks failed commands and authentication events associated
# with ACLs. The ACL Log is useful to troubleshoot failed commands blocked # with ACLs. The ACL Log is useful to troubleshoot failed commands blocked
# by ACLs. The ACL Log is stored in memory. You can reclaim memory with # by ACLs. The ACL Log is stored in memory. You can reclaim memory with
# ACL LOG RESET. Define the maximum entry length of the ACL Log below. # ACL LOG RESET. Define the maximum entry length of the ACL Log below.
acllog-max-len 128 acllog-max-len 128
@ -895,7 +895,7 @@ acllog-max-len 128
# AUTH <password> as usually, or more explicitly with AUTH default <password> # AUTH <password> as usually, or more explicitly with AUTH default <password>
# if they follow the new protocol: both will work. # if they follow the new protocol: both will work.
# #
# The requirepass is not compatable with aclfile option and the ACL LOAD # The requirepass is not compatible with aclfile option and the ACL LOAD
# command, these will cause requirepass to be ignored. # command, these will cause requirepass to be ignored.
# #
# requirepass foobared # requirepass foobared
@ -903,7 +903,7 @@ acllog-max-len 128
# New users are initialized with restrictive permissions by default, via the # New users are initialized with restrictive permissions by default, via the
# equivalent of this ACL rule 'off resetkeys -@all'. Starting with Redis 6.2, it # equivalent of this ACL rule 'off resetkeys -@all'. Starting with Redis 6.2, it
# is possible to manage access to Pub/Sub channels with ACL rules as well. The # is possible to manage access to Pub/Sub channels with ACL rules as well. The
# default Pub/Sub channels permission if new users is controlled by the # default Pub/Sub channels permission if new users is controlled by the
# acl-pubsub-default configuration directive, which accepts one of these values: # acl-pubsub-default configuration directive, which accepts one of these values:
# #
# allchannels: grants access to all Pub/Sub channels # allchannels: grants access to all Pub/Sub channels
@ -1033,7 +1033,7 @@ acllog-max-len 128
# Eviction processing is designed to function well with the default setting. # Eviction processing is designed to function well with the default setting.
# If there is an unusually large amount of write traffic, this value may need to # If there is an unusually large amount of write traffic, this value may need to
# be increased. Decreasing this value may reduce latency at the risk of # be increased. Decreasing this value may reduce latency at the risk of
# eviction processing effectiveness # eviction processing effectiveness
# 0 = minimum latency, 10 = default, 100 = process without regard to latency # 0 = minimum latency, 10 = default, 100 = process without regard to latency
# #
@ -1495,18 +1495,18 @@ lua-time-limit 5000
# cluster-replica-no-failover no # cluster-replica-no-failover no
# This option, when set to yes, allows nodes to serve read traffic while the # This option, when set to yes, allows nodes to serve read traffic while the
# the cluster is in a down state, as long as it believes it owns the slots. # the cluster is in a down state, as long as it believes it owns the slots.
# #
# This is useful for two cases. The first case is for when an application # This is useful for two cases. The first case is for when an application
# doesn't require consistency of data during node failures or network partitions. # doesn't require consistency of data during node failures or network partitions.
# One example of this is a cache, where as long as the node has the data it # One example of this is a cache, where as long as the node has the data it
# should be able to serve it. # should be able to serve it.
# #
# The second use case is for configurations that don't meet the recommended # The second use case is for configurations that don't meet the recommended
# three shards but want to enable cluster mode and scale later. A # three shards but want to enable cluster mode and scale later. A
# master outage in a 1 or 2 shard configuration causes a read/write outage to the # master outage in a 1 or 2 shard configuration causes a read/write outage to the
# entire cluster without this option set, with it set there is only a write outage. # entire cluster without this option set, with it set there is only a write outage.
# Without a quorum of masters, slot ownership will not change automatically. # Without a quorum of masters, slot ownership will not change automatically.
# #
# cluster-allow-reads-when-down no # cluster-allow-reads-when-down no