]>
Commit | Line | Data |
---|---|---|
be2be3d9 | 1 | # Example sentinel.conf |
6b5daa2d | 2 | |
23023fc6 | 3 | # port <sentinel-port> |
4 | # The port that this sentinel instance will run on | |
5 | port 26379 | |
6 | ||
7 | # sentinel monitor <name> <ip> <redis-port> <quorum> | |
8 | # Tells Sentinel to monitor this slave, and to consider it in O_DOWN | |
9 | # (Objectively Down) state only if at least <quorum> sentinels agree. | |
6b5daa2d | 10 | # |
11 | # Note: master name should not include special characters or spaces. | |
12 | # The valid charset is A-z 0-9 and the three characters ".-_". | |
13 | sentinel monitor mymaster 127.0.0.1 6379 2 | |
14 | ||
23023fc6 | 15 | # sentinel down-after-milliseconds <mymaster> <milliseconds> |
6b5daa2d | 16 | # Number of milliseconds the master (or any attached slave or sentinel) should |
17 | # be unreachable (as in, not acceptable reply to PING, continuously, for the | |
18 | # specified period) in order to consider it in S_DOWN state (Subjectively | |
19 | # Down). | |
20 | # | |
21 | # Default is 30 seconds. | |
22 | sentinel down-after-milliseconds mymaster 30000 | |
23 | ||
23023fc6 | 24 | # sentinel can-failover <mymaster> <yes|no> |
6b5daa2d | 25 | # Specify if this Sentinel can start the failover for this master. |
26 | sentinel can-failover mymaster yes | |
27 | ||
23023fc6 | 28 | # sentinel parallel-syncs <mymaster> <numslaves> |
6b5daa2d | 29 | # How many slaves we can reconfigure to point to the new slave simultaneously |
30 | # during the failover. Use a low number if you use the slaves to serve query | |
31 | # to avoid that all the slaves will be unreachable at about the same | |
32 | # time while performing the synchronization with the master. | |
33 | sentinel parallel-syncs mymaster 1 | |
34 | ||
23023fc6 | 35 | # sentinel failover-timeout <mymaster> <milliseconds> |
6b5daa2d | 36 | # Specifies the failover timeout in milliseconds. When this time has elapsed |
37 | # without any progress in the failover process, it is considered concluded by | |
38 | # the sentinel even if not all the attached slaves were correctly configured | |
39 | # to replicate with the new master (however a "best effort" SLAVEOF command | |
40 | # is sent to all the slaves before). | |
41 | # | |
42 | # Also when 25% of this time has elapsed without any advancement, and there | |
43 | # is a leader switch (the sentinel did not started the failover but is now | |
44 | # elected as leader), the sentinel will continue the failover doing a | |
45 | # "takeover". | |
46 | # | |
47 | # Default is 15 minutes. | |
48 | sentinel failover-timeout mymaster 900000 | |
49 |