2012-07-23 13:06:55 +00:00
|
|
|
# Example sentinel.conf
|
2012-07-23 10:54:52 +00:00
|
|
|
|
2012-07-25 13:52:26 +00:00
|
|
|
# port <sentinel-port>
|
|
|
|
|
# The port that this sentinel instance will run on
|
|
|
|
|
port 26379
|
|
|
|
|
|
2012-07-25 14:33:37 +00:00
|
|
|
# sentinel monitor <master-name> <ip> <redis-port> <quorum>
|
|
|
|
|
#
|
2012-07-25 13:52:26 +00:00
|
|
|
# Tells Sentinel to monitor this slave, and to consider it in O_DOWN
|
|
|
|
|
# (Objectively Down) state only if at least <quorum> sentinels agree.
|
2012-07-23 10:54:52 +00:00
|
|
|
#
|
|
|
|
|
# Note: master name should not include special characters or spaces.
|
|
|
|
|
# The valid charset is A-z 0-9 and the three characters ".-_".
|
|
|
|
|
sentinel monitor mymaster 127.0.0.1 6379 2
|
|
|
|
|
|
2012-07-25 14:33:37 +00:00
|
|
|
# sentinel down-after-milliseconds <master-name> <milliseconds>
|
|
|
|
|
#
|
2012-07-23 10:54:52 +00:00
|
|
|
# Number of milliseconds the master (or any attached slave or sentinel) should
|
|
|
|
|
# be unreachable (as in, not acceptable reply to PING, continuously, for the
|
|
|
|
|
# specified period) in order to consider it in S_DOWN state (Subjectively
|
|
|
|
|
# Down).
|
|
|
|
|
#
|
|
|
|
|
# Default is 30 seconds.
|
|
|
|
|
sentinel down-after-milliseconds mymaster 30000
|
|
|
|
|
|
2012-07-25 14:33:37 +00:00
|
|
|
# sentinel can-failover <master-name> <yes|no>
|
|
|
|
|
#
|
2012-07-23 10:54:52 +00:00
|
|
|
# Specify if this Sentinel can start the failover for this master.
|
|
|
|
|
sentinel can-failover mymaster yes
|
|
|
|
|
|
2012-07-25 14:33:37 +00:00
|
|
|
# sentinel parallel-syncs <master-name> <numslaves>
|
|
|
|
|
#
|
2012-07-23 10:54:52 +00:00
|
|
|
# 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
|
|
|
|
|
# to avoid that all the slaves will be unreachable at about the same
|
|
|
|
|
# time while performing the synchronization with the master.
|
|
|
|
|
sentinel parallel-syncs mymaster 1
|
|
|
|
|
|
2012-07-25 14:33:37 +00:00
|
|
|
# sentinel failover-timeout <master-name> <milliseconds>
|
|
|
|
|
#
|
2012-07-23 10:54:52 +00:00
|
|
|
# Specifies the failover timeout in milliseconds. When this time has elapsed
|
|
|
|
|
# without any progress in the failover process, it is considered concluded by
|
|
|
|
|
# the sentinel even if not all the attached slaves were correctly configured
|
|
|
|
|
# to replicate with the new master (however a "best effort" SLAVEOF command
|
|
|
|
|
# is sent to all the slaves before).
|
|
|
|
|
#
|
|
|
|
|
# Also when 25% of this time has elapsed without any advancement, and there
|
|
|
|
|
# is a leader switch (the sentinel did not started the failover but is now
|
|
|
|
|
# elected as leader), the sentinel will continue the failover doing a
|
|
|
|
|
# "takeover".
|
|
|
|
|
#
|
|
|
|
|
# Default is 15 minutes.
|
|
|
|
|
sentinel failover-timeout mymaster 900000
|
|
|
|
|
|
2012-07-25 14:33:37 +00:00
|
|
|
# sentinel notification-script <master-name> <script-path>
|
|
|
|
|
#
|
|
|
|
|
# Call the specified notification script for any sentienl event that is
|
|
|
|
|
# generated in the WARNING level (for instance -sdown, -odown, and so forth).
|
|
|
|
|
# This script should notify the system administrator via email, SMS, or any
|
|
|
|
|
# other messaging system, that there is something wrong with the monitored
|
|
|
|
|
# Redis systems.
|
|
|
|
|
#
|
|
|
|
|
# The script is called with just two arguments: the first is the event type
|
|
|
|
|
# and the second the event description.
|
|
|
|
|
#
|
|
|
|
|
# The script must be exits and executable in order for sentinel to start if
|
|
|
|
|
# this option is provided.
|
|
|
|
|
#
|
|
|
|
|
# Example:
|
|
|
|
|
#
|
|
|
|
|
# sentinel notification-script mymaster /var/redis/notify.sh
|
|
|
|
|
|
|
|
|
|
|
