redis.conf

This commit is contained in:
LingZhaoHui 2020-09-18 23:39:09 +08:00
parent 97df33e599
commit 1aaf124580

View File

@ -142,7 +142,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
# Configure a DH parameters file to enable Diffie-Hellman (DH) key exchange: # Configure a DH parameters file to enable Diffie-Hellman (DH) key exchange:
@ -203,7 +203,7 @@ tcp-keepalive 300
# By default Redis does not run as a daemon. Use 'yes' if you need it. # By default Redis does not run as a daemon. Use 'yes' if you need it.
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized. # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
daemonize no daemonize yes
# If you run Redis from upstart or systemd, Redis can interact with your # If you run Redis from upstart or systemd, Redis can interact with your
# supervision tree. Options: # supervision tree. Options:
@ -744,8 +744,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
@ -1272,18 +1272,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