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