redis/redis-7/redis.conf

279 #    a given number of slaves.
280 # 2) Redis slaves are able to perform a partial resynchronization with the
285 #    network partition slaves automatically try to reconnect to masters
316 # Since Redis 2.6 by default slaves are read-only.
318 # Note: read only slaves are not designed to be exposed to untrusted clients
322 # security of read only slaves using 'rename-command' to shadow all the
332 # New slaves and reconnecting slaves that are not able to continue the replication
334 # synchronization". An RDB file is transmitted from the master to the slaves.
339 #                 process to the slaves incrementally.
343 # With disk-backed replication, while the RDB file is generated, more slaves
346 # the transfer starts, new slaves arriving will be queued and a new transfer
350 # time (in seconds) before starting the transfer in the hope that multiple slaves
359 # to the slaves.
362 # new slaves arriving, that will be queued for the next RDB transfer, so the server
363 # waits a delay in order to let more slaves arrive.
369 # Slaves send PINGs to server in a predefined interval. It's possible to change
378 # 2) Master timeout from the point of view of slaves (data, pings).
390 # less bandwidth to send data to slaves. But this can add a delay for
398 # or when the master and slaves are many hops away, turning this to "yes" may
403 # slave data when slaves are disconnected for some time, so that when a slave
415 # After a master has no longer connected slaves for some time, the backlog
420 # Note that slaves never free the backlog for timeout, since they may be
422 # resynchronize" with the slaves: hence they should always accumulate backlog.
433 # for instance if there are three slaves with priority 10, 100, 25 Sentinel will
444 # N slaves connected, having a lag less or equal than M seconds.
446 # The N slaves need to be in "online" state.
452 # will limit the window of exposure for lost writes in case not enough slaves
455 # For example to require at least 3 slaves with a lag <= 10 seconds use:
457 # min-slaves-to-write 3
458 # min-slaves-max-lag 10
462 # By default min-slaves-to-write is set to 0 (feature disabled) and
463 # min-slaves-max-lag is set to 10.
466 # slaves in different ways. For example the "INFO replication" section
526 # AOF file or transmitted to slaves may cause problems.
555 # WARNING: If you have slaves attached to an instance with maxmemory on,
556 # the size of the output buffers needed to feed the slaves are subtracted
559 # buffer of slaves is full with DELs of keys evicted triggering the deletion
562 # In short... if you have slaves attached it is suggested that you set a lower
844 # 1) If there are multiple slaves able to failover, they exchange messages
847 #    Slaves will try to get their rank by offset, and apply to the start
868 # A large slave-validity-factor may allow slaves with too old data to failover
873 # to a value of 0, which means, that slaves will always try to failover the
883 # Cluster slaves are able to migrate to orphaned masters, that are masters
884 # that are left without working slaves. This improves the cluster ability
886 # in case of failure if it has no working slaves.
888 # Slaves migrate to orphaned masters only if there are still at least a
889 # given number of other working slaves for their old master. This number
892 # and so forth. It usually reflects the number of slaves you want for every
895 # Default is 1 (slaves migrate only if their masters remain with at least
1158 # subscribers and slaves receive data in a push fashion.