# Example sentinel.conf

# *** IMPORTANT ***

#

# By default Sentinel will not be reachable from interfaces different than

# localhost, either use the 'bind' directive to bind to a list of network

# interfaces, or disable protected mode with "protected-mode no" by

# adding it to this configuration file.

#

# Before doing that MAKE SURE the instance is protected from the outside

# world via firewalling or other means.

#

# For example you may use one of the following:

#

# bind 127.0.0.1 192.168.1.1

#

# protected-mode no

# port

# The port that this sentinel instance will run on

# sentinel實(shí)例運(yùn)行的端口

port 26379

# 哨兵將會在gossip hello消息中使用指定的ip地址，而不是自動(dòng)發(fā)現(xiàn)的本地地址。

# sentinel announce-ip

# 哨兵會使用指定的端口

# sentinel announce-port

# sentinel 沒必要同時(shí)使用，可以單獨(dú)使用

#

# The above two configuration directives are useful in environments where,

# because of NAT, Sentinel is reachable from outside via a non-local address.

#

# When announce-ip is provided, the Sentinel will claim the specified IP address

# in HELLO messages used to gossip its presence, instead of auto-detecting the

# local address as it usually does.

#

# Similarly when announce-port is provided and is valid and non-zero, Sentinel

# will announce the specified TCP port.

#

# The two options don't need to be used together, if only announce-ip is

# provided, the Sentinel will announce the specified IP and the server port

# as specified by the "port" option. If only announce-port is provided, the

# Sentinel will announce the auto-detected local IP and the specified port.

#

# Example:

#

# sentinel announce-ip 1.2.3.4

# dir

# Every long running process should have a well-defined working directory.

# For Redis Sentinel to chdir to /tmp at startup is the simplest thing

# for the process to don't interfere with administrative tasks such as

# unmounting filesystems.

dir /tmp

# sentinel monitor

# master-name : master Redis Server名稱

# ip : master Redis Server的IP地址

# redis-port : master Redis Server的端口號

# quorum : 主實(shí)例判斷為失效至少需要 quorum 個(gè) Sentinel 進(jìn)程的同意，只要同意 Sentinel 的數(shù)量不達(dá)標(biāo)，自動(dòng)failover就不會執(zhí)行

# 哨兵監(jiān)控這個(gè)master，在至少quorum個(gè)哨兵實(shí)例都認(rèn)為master down后把master標(biāo)記為odown（objective down客觀down；相對應(yīng)的存在sdown，subjective down，主觀down）狀態(tài)。# slaves是自動(dòng)發(fā)現(xiàn)，所以你沒必要明確指定slaves。master名字不能包含特殊的字符或者空格，合法的字符是a-z 0-9和'.''-''_'這個(gè)三個(gè)字符。

# Tells Sentinel to monitor this master, and to consider it in O_DOWN

# (Objectively Down) state only if at least sentinels agree.

#

# Note that whatever is the ODOWN quorum, a Sentinel will require to

# be elected by the majority of the known Sentinels in order to

# start a failover, so no failover can be performed in minority.

#

# Slaves are auto-discovered, so you don't need to specify slaves in

# any way. Sentinel itself will rewrite this configuration file adding

# the slaves using additional configuration options.

# Also note that the configuration file is rewritten when a

# slave is promoted to master.

#

# 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

# sentinel auth-pass

# 設(shè)置master和slaves驗(yàn)證密碼，在監(jiān)控redis實(shí)例時(shí)很有用。

# 如果你想監(jiān)控masters和slaves而設(shè)置不同的密碼，這樣是達(dá)不到目的的。

# Set the password to use to authenticate with the master and slaves.

# Useful if there is a password set in the Redis instances to monitor.

#

# Note that the master password is also used for slaves, so it is not

# possible to set a different password in masters and slaves instances

# if you want to be able to monitor these instances with Sentinel.

#

# However you can have Redis instances without the authentication enabled

# mixed with Redis instances requiring the authentication (as long as the

# password set is the same for all the instances requiring the password) as

# the AUTH command will have no effect in Redis instances with authentication

# switched off.

#

# Example:

#

# sentinel auth-pass mymaster MySUPER--secret-0123passw0rd

# sentinel down-after-milliseconds

# master或slave多長時(shí)間（默認(rèn)30秒）不能使用后標(biāo)記為s_down狀態(tài)。

# 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

# sentinel parallel-syncs

# 選項(xiàng)指定了在執(zhí)行故障轉(zhuǎn)移時(shí)， 最多可以有多少個(gè)從Redis實(shí)例在同步新的主實(shí)例，

# 在從Redis實(shí)例較多的情況下這個(gè)數(shù)字越小，同步的時(shí)間越長，完成故障轉(zhuǎn)移所需的時(shí)間就越長。

# 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

# sentinel failover-timeout

# 如果在該時(shí)間（ms）內(nèi)未能完成failover操作，則認(rèn)為該failover失敗

# 默認(rèn)3分鐘? 單位毫秒

#使用方式：

1）相鄰前后兩次failover的時(shí)間間隔

2）slave錯(cuò)誤的配置為master多長時(shí)間后重新配置

3）正在進(jìn)行的failover，發(fā)現(xiàn)配置沒變，多長時(shí)間后取消failover

4）slaves被配置為新master的slave后，多長時(shí)間后有可能被重新配置

# Specifies the failover timeout in milliseconds. It is used in many ways:

#

# - The time needed to re-start a failover after a previous failover was

#? already tried against the same master by a given Sentinel, is two

#? times the failover timeout.

#

# - The time needed for a slave replicating to a wrong master according

#? to a Sentinel current configuration, to be forced to replicate

#? with the right master, is exactly the failover timeout (counting since

#? the moment a Sentinel detected the misconfiguration).

#

# - The time needed to cancel a failover that is already in progress but

#? did not produced any configuration change (SLAVEOF NO ONE yet not

#? acknowledged by the promoted slave).

#

# - The maximum time a failover in progress waits for all the slaves to be

#? reconfigured as slaves of the new master. However even after this time

#? the slaves will be reconfigured by the Sentinels anyway, but not with

#? the exact parallel-syncs progression as specified.

#

# Default is 3 minutes.

sentinel failover-timeout mymaster 180000

# SCRIPTS EXECUTION

# 指定sentinel檢測到該監(jiān)控的redis實(shí)例指向的實(shí)例異常時(shí)，調(diào)用的報(bào)警腳本。該配置項(xiàng)可選，但是很常用。執(zhí)行規(guī)則如下：

1）如果腳本返回1退出，會重試（最大次數(shù)是10次）

2）如果腳本返回2退出，不重試

3）如果腳本收到一個(gè)信號終止，行為和1）相同

4）腳本有最大運(yùn)行時(shí)間（60秒），超過這個(gè)限制，腳本會被一個(gè)sigkill終止并且會被重試

# sentinel notification-script and sentinel reconfig-script are used in order

# to configure scripts that are called to notify the system administrator

# or to reconfigure clients after a failover. The scripts are executed

# with the following rules for error handling:

#

# If script exits with "1" the execution is retried later (up to a maximum

# number of times currently set to 10).

#

# If script exits with "2" (or an higher value) the script execution is

# not retried.

#

# If script terminates because it receives a signal the behavior is the same

# as exit code 1.

#

# A script has a maximum running time of 60 seconds. After this limit is

# reached the script is terminated with a SIGKILL and the execution retried.

# NOTIFICATION SCRIPT

#

# sentinel notification-script

#

# Call the specified notification script for any sentinel 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 exist and be executable in order for sentinel to start if

# this option is provided.

#

# Example:

#

# sentinel notification-script mymaster /var/redis/notify.sh

# CLIENTS RECONFIGURATION SCRIPT

#

# sentinel client-reconfig-script

#

# When the master changed because of a failover a script can be called in

# order to perform application-specific tasks to notify the clients that the

# configuration has changed and the master is at a different address.

#

# The following arguments are passed to the script:

#

#

#

# is currently always "failover"

# is either "leader" or "observer"

#

# The arguments from-ip, from-port, to-ip, to-port are used to communicate

# the old address of the master and the new address of the elected slave

# (now a master).

#

# This script should be resistant to multiple invocations.

#

# Example:

#

# sentinel client-reconfig-script mymaster /var/redis/reconfig.sh

設(shè)置log文件路徑：

logfile /var/log/redis_6379.log

設(shè)置后臺運(yùn)行：

daemonize yes