Redis学习记录之配置文件(四)

集群：sentienl.conf配置文件

# Example sentinel.conf# port <sentinel-port># The port that this sentinel instance will run on#这个端口是sentienl实例运行的端口port 26379# sentinel announce-ip <ip># sentinel announce-port <port>## The above two configuration directives are useful in environments where,# because of NAT, Sentinel is reachable from outside via a non-local address.#上面的两个配置指令的环境中非常有用,#因为NAT,Sentinel是可以从外面通过非本地地址。# 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.#当提供announce-ip时，sentienl会把消息发送到指定ip，而不是本地ip# Similarly when announce-port is provided and is valid and non-zero, Sentinel# will announce the specified TCP port.#同样，当提供announce-port时，sentienl会把消息发送到这个端口号中，单端口必须是有效的非0端口# 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.#两个选项不需要一起使用,如果只有announce-ip,sentienl将把消息发到指定的IP和服务器端口，指定的“端口”选项。如果只提供announce-port,#sentienl将把消息发到本地IP和指定的端口。# Example:## sentinel announce-ip 1.2.3.4# dir <working-directory># 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.#对 Redis Sentinel在/ tmp目录启动是最简单的事情，因为这个进程不会干扰管理任务例如：卸载文件系统dir /tmp# sentinel monitor <master-name> <ip> <redis-port> <quorum>## Tells Sentinel to monitor this master, and to consider it in O_DOWN# (Objectively Down) state only if at least <quorum> sentinels agree.#只要名称为quorum这个服务通过，就会值监听这个sentienl# 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.#注意：如果odown集群主机宕机，那么会选择其他的运行较少的从机器作为主机# 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.#从sentienl是自动切换的，你不需要特别设置，sentienl自身重写配置文件添加到从服务器中。当主服务宕机，从服务器自动提升为主服务器# Note: master name should not include special characters or spaces.# The valid charset is A-z 0-9 and the three characters ".-_".#注意:主名称不能包含特殊字符或空格。#有效的字符集包括A-z 0-9 和“.-_”这3个sentinel monitor mymaster 127.0.0.1 6379 2# sentinel auth-pass <master-name> <password>## 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.#设置密码来进行身份验证的主从服务器#如果有密码设置在sentienl实例监控是非常有用的# 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.#如果你希望sentienl同事监听这些服务，是不可以设置不同的主从实例服务密码的，# 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-name> <milliseconds>## 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).#设置宕机时间，当连续ping主机或从机多少时间之后没反应，自动切换# Default is 30 seconds.sentinel down-after-milliseconds mymaster 30000# sentinel parallel-syncs <master-name> <numslaves>## 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 <master-name> <milliseconds>## 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 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:#sentinel notification-script和sentinel reconfig-script用于配置脚本,称为通知系统管理员#后或重新配置客户端故障转移。执行脚本有以下错误处理规则:# If script exits with "1" the execution is retried later (up to a maximum# number of times currently set to 10).#如果脚本以‘1’退出执行稍后重试(目前最大次数设置为10)# If script exits with "2" (or an higher value) the script execution is# not retried.#如果脚本以‘2’退出并显示(或一个更高的价值)脚本执行不重试。# If script terminates because it receives a signal the behavior is the same# as exit code 1.#如果脚本终止,因为它收到一个信号的行为是相同的退出代码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.#一个脚本的最大运行时间60秒。在这个极限达到，脚本终止SIGKILL执行重试# NOTIFICATION SCRIPT## sentinel notification-script <master-name> <script-path># # 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 <master-name> <script-path>## 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:## <master-name> <role> <state> <from-ip> <from-port> <to-ip> <to-port>## <state> is currently always "failover"# <role> 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

翻译烂的要死，自己都看不下去了，大家参考下就可以了！