gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

Example redis.conf: stay under 80 cols.

Browse Source
This commit is contained in:
antirez 2019-07-24 11:38:11 +02:00
parent 32efd9adf8
commit 0b780a5477
1 changed files with 33 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

64
redis.conf
View File

@ -336,9 +336,11 @@ replica-read-only yes
# Replication SYNC strategy: disk or socket. # Replication SYNC strategy: disk or socket.
# #
# New replicas and reconnecting replicas that are not able to continue the replication # New replicas and reconnecting replicas that are not able to continue the
# process just receiving differences, need to do what is called a "full # replication process just receiving differences, need to do what is called a
# synchronization". An RDB file is transmitted from the master to the replicas. # "full synchronization". An RDB file is transmitted from the master to the
# replicas.
#
# The transmission can happen in two different ways: # The transmission can happen in two different ways:
# #
# 1) Disk-backed: The Redis master creates a new process that writes the RDB # 1) Disk-backed: The Redis master creates a new process that writes the RDB
@ -348,14 +350,14 @@ replica-read-only yes
# RDB file to replica sockets, without touching the disk at all. # RDB file to replica sockets, without touching the disk at all.
# #
# With disk-backed replication, while the RDB file is generated, more replicas # With disk-backed replication, while the RDB file is generated, more replicas
# can be queued and served with the RDB file as soon as the current child producing # can be queued and served with the RDB file as soon as the current child
# the RDB file finishes its work. With diskless replication instead once # producing the RDB file finishes its work. With diskless replication instead
# the transfer starts, new replicas arriving will be queued and a new transfer # once the transfer starts, new replicas arriving will be queued and a new
# will start when the current one terminates. # transfer will start when the current one terminates.
# #
# When diskless replication is used, the master waits a configurable amount of # When diskless replication is used, the master waits a configurable amount of
# time (in seconds) before starting the transfer in the hope that multiple replicas # time (in seconds) before starting the transfer in the hope that multiple
# will arrive and the transfer can be parallelized. # replicas will arrive and the transfer can be parallelized.
# #
# With slow disks and fast (large bandwidth) networks, diskless replication # With slow disks and fast (large bandwidth) networks, diskless replication
# works better. # works better.
@ -366,8 +368,8 @@ repl-diskless-sync no
# to the replicas. # to the replicas.
# #
# This is important since once the transfer starts, it is not possible to serve # This is important since once the transfer starts, it is not possible to serve
# new replicas arriving, that will be queued for the next RDB transfer, so the server # new replicas arriving, that will be queued for the next RDB transfer, so the
# waits a delay in order to let more replicas arrive. # server waits a delay in order to let more replicas arrive.
# #
# The delay is specified in seconds, and by default is 5 seconds. To disable # The delay is specified in seconds, and by default is 5 seconds. To disable
# it entirely just set it to 0 seconds and the transfer will start ASAP. # it entirely just set it to 0 seconds and the transfer will start ASAP.
@ -389,9 +391,9 @@ repl-diskless-sync-delay 5
# sufficient memory, if you don't have it, you risk an OOM kill. # sufficient memory, if you don't have it, you risk an OOM kill.
repl-diskless-load disabled repl-diskless-load disabled
# Replicas send PINGs to server in a predefined interval. It's possible to change # Replicas send PINGs to server in a predefined interval. It's possible to
# this interval with the repl_ping_replica_period option. The default value is 10 # change this interval with the repl_ping_replica_period option. The default
# seconds. # value is 10 seconds.
# #
# repl-ping-replica-period 10 # repl-ping-replica-period 10
@ -423,10 +425,10 @@ repl-diskless-load disabled
repl-disable-tcp-nodelay no repl-disable-tcp-nodelay no
# Set the replication backlog size. The backlog is a buffer that accumulates # Set the replication backlog size. The backlog is a buffer that accumulates
# replica data when replicas are disconnected for some time, so that when a replica # replica data when replicas are disconnected for some time, so that when a
# wants to reconnect again, often a full resync is not needed, but a partial # replica wants to reconnect again, often a full resync is not needed, but a
# resync is enough, just passing the portion of data the replica missed while # partial resync is enough, just passing the portion of data the replica
# disconnected. # missed while disconnected.
# #
# The bigger the replication backlog, the longer the time the replica can be # The bigger the replication backlog, the longer the time the replica can be
# disconnected and later be able to perform a partial resynchronization. # disconnected and later be able to perform a partial resynchronization.
@ -448,13 +450,13 @@ repl-disable-tcp-nodelay no
# #
# repl-backlog-ttl 3600 # repl-backlog-ttl 3600
# The replica priority is an integer number published by Redis in the INFO output. # The replica priority is an integer number published by Redis in the INFO
# It is used by Redis Sentinel in order to select a replica to promote into a # output. It is used by Redis Sentinel in order to select a replica to promote
# master if the master is no longer working correctly. # into a master if the master is no longer working correctly.
# #
# A replica with a low priority number is considered better for promotion, so # A replica with a low priority number is considered better for promotion, so
# for instance if there are three replicas with priority 10, 100, 25 Sentinel will # for instance if there are three replicas with priority 10, 100, 25 Sentinel
# pick the one with priority 10, that is the lowest. # will pick the one with priority 10, that is the lowest.
# #
# However a special priority of 0 marks the replica as not able to perform the # However a special priority of 0 marks the replica as not able to perform the
# role of master, so a replica with priority of 0 will never be selected by # role of master, so a replica with priority of 0 will never be selected by
@ -743,17 +745,17 @@ replica-priority 100
# DEL commands to the replica as keys evict in the master side. # DEL commands to the replica as keys evict in the master side.
# #
# This behavior ensures that masters and replicas stay consistent, and is usually # This behavior ensures that masters and replicas stay consistent, and is usually
# what you want, however if your replica is writable, or you want the replica to have # what you want, however if your replica is writable, or you want the replica
# a different memory setting, and you are sure all the writes performed to the # to have a different memory setting, and you are sure all the writes performed
# replica are idempotent, then you may change this default (but be sure to understand # to the replica are idempotent, then you may change this default (but be sure
# what you are doing). # to understand what you are doing).
# #
# Note that since the replica by default does not evict, it may end using more # Note that since the replica by default does not evict, it may end using more
# memory than the one set via maxmemory (there are certain buffers that may # memory than the one set via maxmemory (there are certain buffers that may
# be larger on the replica, or data structures may sometimes take more memory and so # be larger on the replica, or data structures may sometimes take more memory
# forth). So make sure you monitor your replicas and make sure they have enough # and so forth). So make sure you monitor your replicas and make sure they
# memory to never hit a real out-of-memory condition before the master hits # have enough memory to never hit a real out-of-memory condition before the
# the configured maxmemory setting. # master hits the configured maxmemory setting.
# #
# replica-ignore-maxmemory yes # replica-ignore-maxmemory yes