4 the virtual machine, three of the redis test machine, a sentinel test machine
Launch three redis, including a master, 2 sets from, restart sentinel surveillance, then close the main redis, n
, sentinel surveillance not to switch from services as the main service,
28 Dec 3091: X 17:49:49. 270 # WARNING: The TCP backlog setting of 511 always be enforced because The/proc/sys/net/core/somaxconn is set to The value of The lower 128.
28 Dec 3091: X 17:49:49. 278 # Sentinel ID is 594291 cc54eb098ed061fb53785a4fa642deed76
28 Dec 3091: X 17:49:49. 278 # + monitor master mymaster 192.168.72.133 6379 quorum 2
28 Dec 3091: X 17:49:49. 287 * + slave slave 192.168.72.131:6379 192.168.72.131 6379 @ mymaster 192.168.72.133 6379
28 Dec 3091: X 17:49:49. 288 * + slave slave 192.168.72.132:6379 192.168.72.132 6379 @ mymaster 192.168.72.133 6379
28 Dec 3091: X 17:49:49. 612 * + sentinel sentinel 72 be4a65e81b86235e25f09e47156760c4d29419 192.168.72.131 26379 @ mymaster 192.168.72.133 6379
28 Dec 3091: X 17:49:49. 622 # + new epoch 14
28 Dec 3091: X 17:49:54. 332 # + sdown slave 192.168.72.132:6379 192.168.72.132 6379 @ mymaster 192.168.72.133 6379
28 Dec 3091: X 17:49:54. 332 # + sdown slave 192.168.72.131:6379 192.168.72.131 6379 @ mymaster 192.168.72.133 6379
28 Dec 3091: X 17:49:54. 686 # + sdown sentinel 72 be4a65e81b86235e25f09e47156760c4d29419 192.168.72.131 26379 @ mymaster 192.168.72.133 6379
28 Dec 3091: X 17:49:57. 583 * + sentinel sentinel 44 fb12485271f88fd86fee040e081c8e20e3e2a4 192.168.72.132 26379 @ mymaster 192.168.72.133 6379
28 Dec 3091: X 17:50:19. 385 # + sdown master mymaster 192.168.72.133 6379
28 Dec 3091: X 17:50:19. 489 # + new epoch 15
28 Dec 3091: X 17:50:19. 490 # + vote - for - 72 be4a65e81b86235e25f09e47156760c4d29419 leader 15
28 Dec 3091: X 17:50:20. 539 # + odown master mymaster 192.168.72.133 6379 # quorum 2/2
28 Dec 3091: X 17:50:20. 539 # Next failover delay: I will not start a failover before Wed Dec 28 17:52:19 2016
28 Dec 3091: X 17:52:19. 865 # + new epoch 16
What reason is this excuse me?

CodePudding user response:

Sentinel. Conf configuration:

The port 26379
Sentinel monitor mymaster 192.168.72.133 6379 1
Protected mode - no
Sentinel down - after - milliseconds mymaster 5000
Sentinel failover - timeout mymaster 60000

CodePudding user response:

Problem solved

CodePudding user response:

Configuration and as above but hasn't been dealt with master hung up the sentinel there has been no switching effect only when the original master to restart the saw log output
Failover - abort - no - good - slave master mymaster 192.168.3.8 6379

CodePudding user response:

Problem has been solve all redis. Conf bind 127.0.0.1 to bind 0.0.0.0 redis - 3.2.8 test version

CodePudding user response:

Problem solved, I this is also the problem 3.2.9

CodePudding user response:

Problem solved

CodePudding user response:

Later people in need of learning may have a look, https://blog.csdn.net/smradish/article/details/106130065, basic pit tread