sentinel.conf

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