Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
ruanhaishen
redis
Commits
52f8f4a0
Commit
52f8f4a0
authored
Oct 24, 2014
by
antirez
Browse files
Diskless replication documented inside example redis.conf.
parent
ec3e2397
Changes
1
Show whitespace changes
Inline
Side-by-side
redis.conf
View file @
52f8f4a0
...
@@ -240,6 +240,33 @@ slave-serve-stale-data yes
...
@@ -240,6 +240,33 @@ slave-serve-stale-data yes
# administrative / dangerous commands.
# administrative / dangerous commands.
slave
-
read
-
only
yes
slave
-
read
-
only
yes
# Replication SYNC strategy: disk or socket.
#
# New slaves and reconnecting slaves 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 slaves.
# The transmission can happen in two different ways:
#
# 1) Disk-backed: The Redis master creates a new process that writes the RDB
# file on disk. Later the file is transferred by the parent
# process to the slaves incrementally.
# 2) Diskless: The Redis master creates a new process that directly writes the
# RDB file to slave sockets, without touching the disk at all.
#
# With disk-backed replication, while the RDB file is generated, more slaves
# 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 slaves 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 slaves
# will arrive and the transfer can be parallelized.
#
# With slow disks and fast (large bandwidth) networks, diskless replication
# works better.
repl
-
diskless
-
sync
no
# Slaves send PINGs to server in a predefined interval. It's possible to change
# Slaves send PINGs to server in a predefined interval. It's possible to change
# this interval with the repl_ping_slave_period option. The default value is 10
# this interval with the repl_ping_slave_period option. The default value is 10
# seconds.
# seconds.
...
...
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