Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ruanhaishen
redis
Commits
0b780a54
Commit
0b780a54
authored
Jul 24, 2019
by
antirez
Browse files
Example redis.conf: stay under 80 cols.
parent
32efd9ad
Changes
1
Hide whitespace changes
Inline
Side-by-side
redis.conf
View file @
0b780a54
...
...
@@ -336,9 +336,11 @@ replica-read-only yes
# Replication SYNC strategy: disk or socket.
#
# New replicas and reconnecting replicas that are not able to continue the replication
# process just receiving differences, need to do what is called a "full
# synchronization". An RDB file is transmitted from the master to the replicas.
# New replicas and reconnecting replicas that are not able to continue the
# replication process just receiving differences, need to do what is called a
# "full synchronization". An RDB file is transmitted from the master to the
# replicas.
#
# The transmission can happen in two different ways:
#
# 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.
#
# 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
# the RDB file finishes its work. With diskless replication instead
once
# the transfer starts, new replicas arriving will be queued and a new
transfer
# will start when the current one terminates.
# can be queued and served with the RDB file as soon as the current child
#
producing
the RDB file finishes its work. With diskless replication instead
#
once
the transfer starts, new replicas arriving will be queued and a new
#
transfer
will start when the current one terminates.
#
# 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
# will arrive and the transfer can be parallelized.
# time (in seconds) before starting the transfer in the hope that multiple
#
replicas
will arrive and the transfer can be parallelized.
#
# With slow disks and fast (large bandwidth) networks, diskless replication
# works better.
...
...
@@ -366,8 +368,8 @@ repl-diskless-sync no
# to the replicas.
#
# 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
# waits a delay in order to let more replicas arrive.
# new replicas arriving, that will be queued for the next RDB transfer, so the
#
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
# 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.
repl
-
diskless
-
load
disabled
# Replicas send PINGs to server in a predefined interval. It's possible to
change
# this interval with the repl_ping_replica_period option. The default
value is 10
# seconds.
# Replicas send PINGs to server in a predefined interval. It's possible to
#
change
this interval with the repl_ping_replica_period option. The default
#
value is 10
seconds.
#
# repl-ping-replica-period 10
...
...
@@ -423,10 +425,10 @@ repl-diskless-load disabled
repl
-
disable
-
tcp
-
nodelay
no
# 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
# wants to reconnect again, often a full resync is not needed, but a
partial
# resync is enough, just passing the portion of data the replica
missed while
# disconnected.
# replica data when replicas are disconnected for some time, so that when a
#
replica
wants to reconnect again, often a full resync is not needed, but a
#
partial
resync is enough, just passing the portion of data the replica
#
missed while
disconnected.
#
# The bigger the replication backlog, the longer the time the replica can be
# disconnected and later be able to perform a partial resynchronization.
...
...
@@ -448,13 +450,13 @@ repl-disable-tcp-nodelay no
#
# repl-backlog-ttl 3600
# The replica priority is an integer number published by Redis in the INFO
output.
# It is used by Redis Sentinel in order to select a replica to promote
into a
# master if the master is no longer working correctly.
# The replica priority is an integer number published by Redis in the INFO
#
output.
It is used by Redis Sentinel in order to select a replica to promote
#
into a
master if the master is no longer working correctly.
#
# 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
# pick the one with priority 10, that is the lowest.
# for instance if there are three replicas with priority 10, 100, 25 Sentinel
#
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
# 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.
#
# 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
# a different memory setting, and you are sure all the writes performed
to the
# replica are idempotent, then you may change this default (but be sure
to understand
# what you are doing).
# what you want, however if your replica is writable, or you want the replica
#
to have
a different memory setting, and you are sure all the writes performed
#
to the
replica are idempotent, then you may change this default (but be sure
#
to understand
what you are doing).
#
# 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
# be larger on the replica, or data structures may sometimes take more memory
and so
# forth). So make sure you monitor your replicas and make sure they
have enough
# memory to never hit a real out-of-memory condition before the
master hits
# the configured maxmemory setting.
# be larger on the replica, or data structures may sometimes take more memory
#
and so
forth). So make sure you monitor your replicas and make sure they
#
have enough
memory to never hit a real out-of-memory condition before the
#
master hits
the configured maxmemory setting.
#
# replica-ignore-maxmemory yes
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment