Some cleanup in sentinel.conf
This commit is contained in:
parent
9e5bef38e6
commit
23023fc626
@ -1,13 +1,18 @@
|
|||||||
# Example sentinel.conf
|
# Example sentinel.conf
|
||||||
|
|
||||||
# sentinel monitor <name> <ip> <port> quorum. Tells Sentinel to monitor this
|
# port <sentinel-port>
|
||||||
# slave, and to consider it in O_DOWN (Objectively Down) state only if at
|
# The port that this sentinel instance will run on
|
||||||
# least <quorum> sentinels agree.
|
port 26379
|
||||||
|
|
||||||
|
# sentinel monitor <name> <ip> <redis-port> <quorum>
|
||||||
|
# Tells Sentinel to monitor this slave, and to consider it in O_DOWN
|
||||||
|
# (Objectively Down) state only if at least <quorum> sentinels agree.
|
||||||
#
|
#
|
||||||
# Note: master name should not include special characters or spaces.
|
# Note: master name should not include special characters or spaces.
|
||||||
# The valid charset is A-z 0-9 and the three characters ".-_".
|
# The valid charset is A-z 0-9 and the three characters ".-_".
|
||||||
sentinel monitor mymaster 127.0.0.1 6379 2
|
sentinel monitor mymaster 127.0.0.1 6379 2
|
||||||
|
|
||||||
|
# sentinel down-after-milliseconds <mymaster> <milliseconds>
|
||||||
# Number of milliseconds the master (or any attached slave or sentinel) should
|
# Number of milliseconds the master (or any attached slave or sentinel) should
|
||||||
# be unreachable (as in, not acceptable reply to PING, continuously, for the
|
# be unreachable (as in, not acceptable reply to PING, continuously, for the
|
||||||
# specified period) in order to consider it in S_DOWN state (Subjectively
|
# specified period) in order to consider it in S_DOWN state (Subjectively
|
||||||
@ -16,15 +21,18 @@ sentinel monitor mymaster 127.0.0.1 6379 2
|
|||||||
# Default is 30 seconds.
|
# Default is 30 seconds.
|
||||||
sentinel down-after-milliseconds mymaster 30000
|
sentinel down-after-milliseconds mymaster 30000
|
||||||
|
|
||||||
|
# sentinel can-failover <mymaster> <yes|no>
|
||||||
# Specify if this Sentinel can start the failover for this master.
|
# Specify if this Sentinel can start the failover for this master.
|
||||||
sentinel can-failover mymaster yes
|
sentinel can-failover mymaster yes
|
||||||
|
|
||||||
|
# sentinel parallel-syncs <mymaster> <numslaves>
|
||||||
# How many slaves we can reconfigure to point to the new slave simultaneously
|
# How many slaves we can reconfigure to point to the new slave simultaneously
|
||||||
# during the failover. Use a low number if you use the slaves to serve query
|
# during the failover. Use a low number if you use the slaves to serve query
|
||||||
# to avoid that all the slaves will be unreachable at about the same
|
# to avoid that all the slaves will be unreachable at about the same
|
||||||
# time while performing the synchronization with the master.
|
# time while performing the synchronization with the master.
|
||||||
sentinel parallel-syncs mymaster 1
|
sentinel parallel-syncs mymaster 1
|
||||||
|
|
||||||
|
# sentinel failover-timeout <mymaster> <milliseconds>
|
||||||
# Specifies the failover timeout in milliseconds. When this time has elapsed
|
# Specifies the failover timeout in milliseconds. When this time has elapsed
|
||||||
# without any progress in the failover process, it is considered concluded by
|
# without any progress in the failover process, it is considered concluded by
|
||||||
# the sentinel even if not all the attached slaves were correctly configured
|
# the sentinel even if not all the attached slaves were correctly configured
|
||||||
|
Loading…
x
Reference in New Issue
Block a user