redis4.0.14哨兵自动故障迁移失败

最新推荐文章于 2024-02-08 12:29:10 发布
最新推荐文章于 2024-02-08 12:29:10 发布
阅读量2.5k 收藏 4
点赞数 2
文章标签： redis
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/lzhfdxhxm/article/details/106675637
版权

错误情况：

哨兵日志信息：

-failover-abort-not-elected

24617:X 10 Jun 21:44:21.323 # +sdown master mymaster 192.168.141.129 6379
24617:X 10 Jun 21:44:21.400 # +odown master mymaster 192.168.141.129 6379 #quorum 3/2
24617:X 10 Jun 21:44:21.400 # +new-epoch 8
24617:X 10 Jun 21:44:21.400 # +try-failover master mymaster 192.168.141.129 6379
24617:X 10 Jun 21:44:21.402 # +vote-for-leader 0e85c75b573140a05addc38543f18cfbb3dc74f3 8
24617:X 10 Jun 21:44:21.402 # a443f3621568e41b03d1a442a0d0ec02b5c7e6be voted for a443f3621568e41b03d1a442a0d0ec02b5c7e6be 8
24617:X 10 Jun 21:44:21.403 # 1a5a45d59dbddeaf1e30b63b27cee5605c0b7ed5 voted for a443f3621568e41b03d1a442a0d0ec02b5c7e6be 8
24617:X 10 Jun 21:44:32.377 # -failover-abort-not-elected master mymaster 192.168.141.129 6379
24617:X 10 Jun 21:44:32.441 # Next failover delay: I will not start a failover before Wed Jun 10 21:50:22 2020

或者：

没有 vote-for-leader

27333:X 10 Jun 22:07:56.622 # +sdown master mymaster 192.168.141.129 6380
27333:X 10 Jun 22:07:58.201 # +sdown slave 127.0.0.1:6379 127.0.0.1 6379 @ mymaster 192.168.141.129 6380
27333:X 10 Jun 22:07:59.292 # +sdown sentinel f0622ba9d068b62c8cab6ceb70fc55f48e94c602 192.168.141.129 26381 @ mymaster 192.168.141.129 6380
27333:X 10 Jun 22:08:00.485 # +sdown sentinel 4785172698bd33321bab5719faaadee10f41907c 192.168.141.129 26380 @ mymaster 192.168.141.129 6380

 

 

redis的配置文件

6379.conf

主要内容：

bind 192.168.141.129 127.0.0.1
protected-mode yes
port 6379

哨兵配置文件：（不正确）

26379.conf

port 26379
sentinel monitor mymaster 192.168.141.129 6379 2

26380.conf

port 26380
sentinel monitor mymaster 192.168.141.129 6379 2

26381.conf

port 26381
sentinel monitor mymaster 192.168.141.129 6379 2

相关命令：

启动6379主服务器：

redis-server 6379.conf

启动6380服务器：

redis-server 6380.conf --slaveof 192.168.141.129 6379

或者

redis-server 6380.conf --slaveof 127.0.0.1 6379

以上两个命令，在哨兵配置正确的情况下都可以。如果哨兵没配置正确（没bind ip），主连接补上后，哨兵的日志会不一样。

启动哨兵：

redis-server 26379.conf --sentinel

 

正确的配置

哨兵配置文件：

26379.conf

根据redis的配置（6379.conf等），在配置文件里加上bind那一行

port 26379
sentinel monitor mymaster 192.168.141.129 6379 2
bind 192.168.141.129 127.0.0.1

或者将monitor里的ip改成127.0.0.1也可以

port 26379
sentinel monitor mymaster 127.0.0.1 6379 2
bind 192.168.141.129 127.0.0.1

26380.conf等一样

 

正确的自动故障迁移日志

26379哨兵

[root@oracle test]# redis-server 26379.conf --sentinel
24588:X 10 Jun 21:26:29.624 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
24588:X 10 Jun 21:26:29.624 # Redis version=4.0.14, bits=64, commit=00000000, modified=0, pid=24588, just started
24588:X 10 Jun 21:26:29.624 # Configuration loaded
24588:X 10 Jun 21:26:29.625 * Increased maximum number of open files to 10032 (it was originally set to 1024).
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 4.0.14 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in sentinel mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 26379
 |    `-._   `._    /     _.-'    |     PID: 24588
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

24588:X 10 Jun 21:26:29.626 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
24588:X 10 Jun 21:26:29.626 # Sentinel ID is 1a5a45d59dbddeaf1e30b63b27cee5605c0b7ed5
24588:X 10 Jun 21:26:29.626 # +monitor master mymaster 192.168.141.129 6379 quorum 2
24588:X 10 Jun 21:26:59.684 # +sdown sentinel a5bfebbed1ead357c6a285d33dab3fa2e3af5537 192.168.141.129 0 @ mymaster 192.168.141.129 6379


--------------------当主连接不上之后：-------------------
24588:X 10 Jun 21:28:32.689 # +sdown master mymaster 192.168.141.129 6379
24588:X 10 Jun 21:28:32.736 # +new-epoch 6
24588:X 10 Jun 21:28:32.737 # +vote-for-leader a443f3621568e41b03d1a442a0d0ec02b5c7e6be 6
24588:X 10 Jun 21:28:32.790 # +odown master mymaster 192.168.141.129 6379 #quorum 4/2
24588:X 10 Jun 21:28:32.790 # Next failover delay: I will not start a failover before Wed Jun 10 21:34:32 2020
24588:X 10 Jun 21:28:33.458 # +config-update-from sentinel a443f3621568e41b03d1a442a0d0ec02b5c7e6be 192.168.141.129 26381 @ mymaster 192.168.141.129 6379
24588:X 10 Jun 21:28:33.458 # +switch-master mymaster 192.168.141.129 6379 192.168.141.129 6381
24588:X 10 Jun 21:28:33.458 * +slave slave 192.168.141.129:6380 192.168.141.129 6380 @ mymaster 192.168.141.129 6381
24588:X 10 Jun 21:28:33.458 * +slave slave 192.168.141.129:6379 192.168.141.129 6379 @ mymaster 192.168.141.129 6381
24588:X 10 Jun 21:29:03.491 # +sdown slave 192.168.141.129:6379 192.168.141.129 6379 @ mymaster 192.168.141.129 6381

26380哨兵

[root@oracle test]# redis-server 26380.conf --sentinel
24617:X 10 Jun 21:26:46.400 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
24617:X 10 Jun 21:26:46.400 # Redis version=4.0.14, bits=64, commit=00000000, modified=0, pid=24617, just started
24617:X 10 Jun 21:26:46.400 # Configuration loaded
24617:X 10 Jun 21:26:46.401 * Increased maximum number of open files to 10032 (it was originally set to 1024).
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 4.0.14 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in sentinel mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 26380
 |    `-._   `._    /     _.-'    |     PID: 24617
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

24617:X 10 Jun 21:26:46.402 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
24617:X 10 Jun 21:26:46.402 # Sentinel ID is 0e85c75b573140a05addc38543f18cfbb3dc74f3
24617:X 10 Jun 21:26:46.402 # +monitor master mymaster 192.168.141.129 6379 quorum 2

24617:X 10 Jun 21:28:32.652 # +sdown master mymaster 192.168.141.129 6379
24617:X 10 Jun 21:28:32.736 # +new-epoch 6
24617:X 10 Jun 21:28:32.737 # +vote-for-leader a443f3621568e41b03d1a442a0d0ec02b5c7e6be 6
24617:X 10 Jun 21:28:33.458 # +config-update-from sentinel a443f3621568e41b03d1a442a0d0ec02b5c7e6be 192.168.141.129 26381 @ mymaster 192.168.141.129 6379
24617:X 10 Jun 21:28:33.458 # +switch-master mymaster 192.168.141.129 6379 192.168.141.129 6381
24617:X 10 Jun 21:28:33.458 * +slave slave 192.168.141.129:6380 192.168.141.129 6380 @ mymaster 192.168.141.129 6381
24617:X 10 Jun 21:28:33.458 * +slave slave 192.168.141.129:6379 192.168.141.129 6379 @ mymaster 192.168.141.129 6381
24617:X 10 Jun 21:29:03.472 # +sdown slave 192.168.141.129:6379 192.168.141.129 6379 @ mymaster 192.168.141.129 6381

 

26381哨兵

[root@oracle test]# redis-server 26381.conf --sentinel
24626:X 10 Jun 21:26:52.408 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
24626:X 10 Jun 21:26:52.408 # Redis version=4.0.14, bits=64, commit=00000000, modified=0, pid=24626, just started
24626:X 10 Jun 21:26:52.408 # Configuration loaded
24626:X 10 Jun 21:26:52.408 * Increased maximum number of open files to 10032 (it was originally set to 1024).
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 4.0.14 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in sentinel mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 26381
 |    `-._   `._    /     _.-'    |     PID: 24626
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

24626:X 10 Jun 21:26:52.409 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
24626:X 10 Jun 21:26:52.410 # Sentinel ID is a443f3621568e41b03d1a442a0d0ec02b5c7e6be
24626:X 10 Jun 21:26:52.410 # +monitor master mymaster 192.168.141.129 6379 quorum 2

24626:X 10 Jun 21:28:32.674 # +sdown master mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:32.733 # +odown master mymaster 192.168.141.129 6379 #quorum 3/2
24626:X 10 Jun 21:28:32.733 # +new-epoch 6
24626:X 10 Jun 21:28:32.733 # +try-failover master mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:32.734 # +vote-for-leader a443f3621568e41b03d1a442a0d0ec02b5c7e6be 6
24626:X 10 Jun 21:28:32.737 # 1a5a45d59dbddeaf1e30b63b27cee5605c0b7ed5 voted for a443f3621568e41b03d1a442a0d0ec02b5c7e6be 6
24626:X 10 Jun 21:28:32.737 # 0e85c75b573140a05addc38543f18cfbb3dc74f3 voted for a443f3621568e41b03d1a442a0d0ec02b5c7e6be 6
24626:X 10 Jun 21:28:32.738 # e1949da6609ebbe9c123e4375179013495f2b230 voted for a443f3621568e41b03d1a442a0d0ec02b5c7e6be 6
24626:X 10 Jun 21:28:32.825 # +elected-leader master mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:32.825 # +failover-state-select-slave master mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:32.902 # +selected-slave slave 192.168.141.129:6381 192.168.141.129 6381 @ mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:32.902 * +failover-state-send-slaveof-noone slave 192.168.141.129:6381 192.168.141.129 6381 @ mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:32.986 * +failover-state-wait-promotion slave 192.168.141.129:6381 192.168.141.129 6381 @ mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:33.385 # +promoted-slave slave 192.168.141.129:6381 192.168.141.129 6381 @ mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:33.385 # +failover-state-reconf-slaves master mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:33.458 * +slave-reconf-sent slave 192.168.141.129:6380 192.168.141.129 6380 @ mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:33.826 # -odown master mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:34.441 * +slave-reconf-inprog slave 192.168.141.129:6380 192.168.141.129 6380 @ mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:34.441 * +slave-reconf-done slave 192.168.141.129:6380 192.168.141.129 6380 @ mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:34.518 # +failover-end master mymaster 192.168.141.129 6379
24626:X 10 Jun 21:28:34.518 # +switch-master mymaster 192.168.141.129 6379 192.168.141.129 6381
24626:X 10 Jun 21:28:34.518 * +slave slave 192.168.141.129:6380 192.168.141.129 6380 @ mymaster 192.168.141.129 6381
24626:X 10 Jun 21:28:34.518 * +slave slave 192.168.141.129:6379 192.168.141.129 6379 @ mymaster 192.168.141.129 6381
24626:X 10 Jun 21:29:04.533 # +sdown slave 192.168.141.129:6379 192.168.141.129 6379 @ mymaster 192.168.141.129 6381

备注、注意事项

哨兵启动之后，会自动修改哨兵的配置文件，比如：

启动前的26379.conf

port 26379
sentinel monitor mymaster 127.0.0.1 6379 2
bind 192.168.141.129 127.0.0.1

启动之后：

port 26379
bind 192.168.141.129 127.0.0.1
sentinel myid e7f398056cc17cdc1d1abf4ddaeff6485881c6e8
# Generated by CONFIG REWRITE
dir "/root/test"
sentinel deny-scripts-reconfig yes
sentinel monitor mymaster 192.168.141.129 6379 2
sentinel config-epoch mymaster 1
sentinel leader-epoch mymaster 1
sentinel known-slave mymaster 192.168.141.129 6380
sentinel known-slave mymaster 192.168.141.129 6381
sentinel known-sentinel mymaster 192.168.141.129 26380 33839d2c5fa9d5af14f89eaef58ac97bbc822523
sentinel known-sentinel mymaster 192.168.141.129 26381 8a3fa6cdd0736d8bc83ef8cfa1babb794f0001c7
sentinel current-epoch 1

redis主服务器（以6379为例）挂掉之后重启，而且如果是在已经自动产生了新的主服务器（以6380为例）的情况下，原主服务器的配置文件6379.conf会被改写，6379重启完自动变成6380的从服务器：

# Generated by CONFIG REWRITE
slaveof 192.168.141.129 6380

重启日志：

注意里面有CONFIG REWRITE操作

30696:M 10 Jun 22:57:49.201 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
30696:M 10 Jun 22:57:49.201 # Server initialized
30696:M 10 Jun 22:57:49.201 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
30696:M 10 Jun 22:57:49.201 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
30696:M 10 Jun 22:57:49.201 * Reading RDB preamble from AOF file...
30696:M 10 Jun 22:57:49.201 * Reading the remaining AOF tail...
30696:M 10 Jun 22:57:49.201 * DB loaded from append only file: 0.000 seconds
30696:M 10 Jun 22:57:49.201 * Ready to accept connections
30696:S 10 Jun 22:57:59.252 * Before turning into a slave, using my master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer.
30696:S 10 Jun 22:57:59.252 * SLAVE OF 192.168.141.129:6380 enabled (user request from 'id=3 addr=192.168.141.129:52622 fd=9 name=sentinel-8a3fa6cd-cmd age=10 idle=0 flags=x db=0 sub=0 psub=0 multi=3 qbuf=0 qbuf-free=32768 obl=36 oll=0 omem=0 events=r cmd=exec')
30696:S 10 Jun 22:57:59.253 # CONFIG REWRITE executed with success.
30696:S 10 Jun 22:57:59.285 * Connecting to MASTER 192.168.141.129:6380
30696:S 10 Jun 22:57:59.285 * MASTER <-> SLAVE sync started
30696:S 10 Jun 22:57:59.285 * Non blocking connect for SYNC fired the event.
30696:S 10 Jun 22:57:59.286 * Master replied to PING, replication can continue...
30696:S 10 Jun 22:57:59.286 * Trying a partial resynchronization (request 71f7c705e36cab2d3194888520c23278f331b63e:1).
30696:S 10 Jun 22:57:59.287 * Full resync from master: c4183d3ac691fcd9fb4831d2aaba82321a2fc8b6:157380
30696:S 10 Jun 22:57:59.287 * Discarding previously cached master state.
30696:S 10 Jun 22:57:59.320 * MASTER <-> SLAVE sync: receiving 198 bytes from master
30696:S 10 Jun 22:57:59.320 * MASTER <-> SLAVE sync: Flushing old data
30696:S 10 Jun 22:57:59.321 * MASTER <-> SLAVE sync: Loading DB in memory
30696:S 10 Jun 22:57:59.321 * MASTER <-> SLAVE sync: Finished with success
30696:S 10 Jun 22:57:59.321 * Background append only file rewriting started by pid 30709
30696:S 10 Jun 22:57:59.371 * AOF rewrite child asks to stop sending diffs.
30709:C 10 Jun 22:57:59.371 * Parent agreed to stop sending diffs. Finalizing AOF...
30709:C 10 Jun 22:57:59.371 * Concatenating 0.00 MB of AOF diff received from parent.
30709:C 10 Jun 22:57:59.371 * SYNC append only file rewrite performed
30709:C 10 Jun 22:57:59.372 * AOF rewrite: 0 MB of memory used by copy-on-write
30696:S 10 Jun 22:57:59.386 * Background AOF rewrite terminated with success
30696:S 10 Jun 22:57:59.386 * Residual parent diff successfully flushed to the rewritten AOF (0.00 MB)
30696:S 10 Jun 22:57:59.386 * Background AOF rewrite finished successfully

redis的主服务器挂掉之后，哨兵会在30s之后自动投票出新的主服务器。而且哨兵的配置文件又会进行修改：

port 26379
bind 192.168.141.129 127.0.0.1
sentinel myid e7f398056cc17cdc1d1abf4ddaeff6485881c6e8
# Generated by CONFIG REWRITE
dir "/root/test"
sentinel deny-scripts-reconfig yes
sentinel monitor mymaster 192.168.141.129 6380 2
sentinel config-epoch mymaster 1
sentinel leader-epoch mymaster 1
sentinel known-slave mymaster 127.0.0.1 6379
sentinel known-slave mymaster 192.168.141.129 6381
sentinel known-sentinel mymaster 192.168.141.129 26380 33839d2c5fa9d5af14f89eaef58ac97bbc822523
sentinel known-sentinel mymaster 192.168.141.129 26381 8a3fa6cdd0736d8bc83ef8cfa1babb794f0001c7
sentinel current-epoch 1

因此，如果需要在原主服务器6379重启之后重新变回主服务器，那么不止6379.conf配置文件要修改（去掉最后一行关于slaveof的配置），哨兵的配置文件也要进行修改。这样redis服务器和哨兵服务器重启之后，6379才能变回主服务器

lzhfdxhxm
关注
  • 2
    点赞
  • 踩
  • 4
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
2022-03-25 redis哨兵处理failover
技术之路
03-25 1538
摘要: 记录redis哨兵模式做failover处理 调用堆栈: #0 sentinelStartFailover (master=0x7fb5d8267000) at sentinel.c:4578 #1 0x00000000004aa628 in sentinelStartFailoverIfNeeded (master=master@entry=0x7fb5d8267000) at sentinel.c:4627 #2 0x00000000004abc41 in sentin..
redis：哨兵选举新的master报错——-failover-abort-no-good-slave master mymaster
aflyingpig11的博客
09-27 333
3.sentinel.config 的sentinel monitor mymaster 和sentinel auth-pass mymaster 也没有错。但在我测试主从复制的时候，发现主从主机无法相连，我在网上找的解决方案的关闭了master主机所在的防火墙。1.我核对了sentinel.config和redis.config bind 绑定的端口。现在master下线了，需要选举新的master，需要关闭新master所在主机的防火墙。2.三台redis masterauth都设置了密码。
使用docker部署redis哨兵(sentinel)时遇到的问题
最新发布
weixin_63028438的博客
02-08 1400
在进行故障迁移（failover）时，我的master是redis1，现在我故意让redis1停止运行，发现sentinel可以正常地修改自己配置文件的master ip为redis2的ip，进入redis2, redis3的客户端输入info replication命令查看，发现redis2确实变成了主机，redis3也变成了redis2的从机，也就是说故障迁移成功。我们知道，odown是需要哨兵投票决定的，要达到一定的票数才能成功执行，现在三个哨兵无法感知对方，也就无法进行客观下线了，这就是问题所在。
-failover-abort-not-elected master mymaster问题
一叶知秋hwb的博客
11-13 2600
redis配置sentinel，master shutdown后主从切换失败，提示错误 -failover-abort-not-elected master mymaster x.x.x.x 6379 原因是sentinel.conf缺少配置，若redis.conf中添加 protected-mode yes bind 0.0.0.0 则sentinel.conf中添加该属性。 ...
redis 哨兵模式启动报错-failover-abort-no-good-slave master Next failover delay: I will not start a failover
热门推荐
不是一枚开发
04-10 4万+
问题： 启用哨兵模式时报错 31812:X 10 Apr 2022 16:15:58.947 # -failover-abort-no-good-slave master mymaster 127.0.0.1 6379 31812:X 10 Apr 2022 16:15:59.014 # Next failover delay: I will not start a failover before Sun Apr 10 16:21:59 2022 原因： 配置sentinel.conf时，没有设置密码 解
-failover-abort-no-good-slave master
weixin_64161454的博客
03-13 955
-failover-abort-no-good-slave masterr 在搭建redis哨兵监听集群状态时出现这个错误这个错误的意思表示选择附属从节点，转换主节点是出了错误，原因是没有好的从节点，根本原因就是没有找到从节点信息，出现这个错误的根本原因是在于我们的哨兵配置文件写错了
ERROR——redis哨兵模式主机挂掉，不能自动选举新的master
weixin_48185643的博客
12-27 2713
这里写目录标题实验环境报错现象解决方法 实验环境 20.0.0.10 (master) 20.0.0.11 (slave) 20.0.0.12 (slave) 报错现象 当我把master shutdown后 sentinel 不能自动选举出新的master并，出现 failover-abort-no-good-slave 错误 解决方法 修改redis.conf 三台全部修改为 bind 0.0.0.0 问题解决！ ...
Redis哨兵模式主服务器宕机后每次选举选举仍然选挂掉的主服务器错误failover-state-select-slave master mymaster报错原因即解决方案
Menghu98621的博客
04-06 1664
报错原因：没有开放所有主从服务器和哨兵节点的端口。 解决方案：开放窗口或关闭防火墙：执行systemctl stop firewalld.service命令。
redis：sentinel配置及测试
Super菜的专栏
07-26 7696
参考原理： http://www.redis.cn/topics/sentinel.html https://segmentfault.com/a/1190000002680804 结构： 192.168.56.159 6379 master 192.168.56.159 6380 slave 192.168.56.159 26379 sentinel 192.168.56.1
spring集成redis——主从配置以及哨兵监控
weixin_33737774的博客
06-05 242
Redis主从模式配置： Redis的主从模式配置是非常简单的，首先我们需要有2个可运行的redis环境： master node : 192.168.56.101 8887 slave node: 192.168.56.102 7777 我们只要在slave 节点的配置文件中，找到slaveof开头 然后修改为：（master的ip与端口） slaveof 192...
gin redis 链接不上_Redis的三种模式：主从、哨兵、集群
weixin_39531688的博客
11-02 251
前言 Redis是一个开源的使用ANSI C语言编写、支持网络、可基于内存亦可持久化的日志型、Key-Value数据库，并提供多种语言的API。普遍用于目前主流的分布式架构系统中，关于redis的详细介绍，见另一篇文章：redis的安装与介绍​blog.csdn.netredis的多机数据库实现，主要分为以下三种：Redis哨兵（Sentinel）Redis复制（主从）Redis集群一、Re...
【Redis】Redis高级：哨兵
qq_50675319的博客
09-25 546
哨兵的作用如下：监控：Sentinel会不断检查master和slave是否按预期工作 自动故障恢复：如果master故障，Sentinel会将一个slave提升为master。当故障的master恢复之后也以新的master为主通知：Sentinel可以充当Redis客户端的服务发现来源，Redis客户端无需再直接连接Redis节点，而是连接Sentinel，由Sentinel提供主从节点的地址信息，当集群发生故障转移，即有slave被提升为master后，Sentinel 会将服务状态的变更通知
Redis哨兵模式启动30秒后日志出现+sdown slave和+sdown master或+sdown sentinel
m0_64284147的博客
07-24 3649
2】各服务器之间不能互相访问，导致部署在各服务器上的redis不能互相通讯，从而在启动哨兵后导致sdownslave和sdownmaster（我这里的哨兵集群使用内网互相访问，若内网之间不能互相访问，也会导致sdownslave和sdownmaster）【1】安全组或防火墙没开放6379端口，导致master和slave之间不能通讯，从而在启动哨兵后导致sdownslave和sdownmaster。【1】给安全组添加规则，开放26379端口（我使用的是华为云，配置仅供参考）......
关于redis多个哨兵sentinel在阿里云的坑 sdown sentinel或者failover-abort-not-elected
qq_41736500的博客
06-07 2538
关于redis多个哨兵sentinel在阿里云的坑sentinel之间不能相互通信的坑解决方案(1)阿里云安全组内网访问(2)推荐:定义sentinel通信被发现的ip地址 sentinel之间不能相互通信的坑 这两天在三台阿里云服务器上搭建redis集群,遇到个问题,试了网上的bind 0.0.0.0和protected-mode no任然还是有问题,网上百度和谷歌了很久,都没有看到网上有解决办法，故记录这个坑，便别人参考。 redis环境: 一主二从三哨兵,都运行在阿里云服务器上 运行主服务器两从服务
redis的sentinel模式故障演练
weixin_34153893的博客
09-12 320
序 本文主要研究一下redis的sentinel模式的failover 启动 docker-compose up 复制代码 这里使用redis-cluster的docker-compose文件进行演示 master日志 1:M 12 Sep 06:42:02.159 # WARNING: The TCP backlog setting of 511 cannot be enforced be...
Ubuntu 12.10下Redis主从复制配置
zzhongcy的专栏
02-25 1646
Ubuntu 12.10下Redis主从复制配置 一、 原理  1.1 redis特点     Redis的主从复制功能非常强大，一个master可以拥有多个slave，而一个slave又可以拥有多个slave，如此下去，形成了强大的多级服务器集群架构。下面是关于redis主从复制的一些特点：      1.master可以有多个slave      2.除了多个slave连到相
redis 远程主机强迫关闭了一个现有的连接。_Linux运维-搭建高可用Redis缓存
weixin_42521186的博客
01-17 1162
搭建Redis1. 下载并解压首先从Redis官网下载Redis并解压，楼主使用的版本是4.0.2。依次执行如下命令：cd /usr/local/wget http://download.redis.io/releases/redis-4.0.2.tar.gztar -zxvf redis-4.0.2.tar.gz如果没有安装gcc依赖包，则安装对应依赖包yum install -y gcc-c+...
redis-3.0.1 sentinel 主从高可用 详细配置
sdlyjzh的专栏
12-12 5096
最近项目上线部署，要求redis作高可用，由于redis cluster还不是特别成熟，就选择了redis sentinel做高可用。生产环境中，一般要求有3个redis节点。但本文为了试验方便，只用了两个节点，一主一从。部署规划172.16.203.10 主节点 172.16.203.4 从节点 redis 3.0.1主节点red
redis 4.0.14
07-28
Redis 4.0.14是Redis数据库的一个版本。Redis是一个开源的内存数据结构存储系统，它具有高性能、灵活性和可扩展性的特点。Redis支持多种数据结构，如字符串、哈希、列表、集合和有序集合，并提供了丰富的命令集用于操作这些数据结构。Redis还支持持久化、复制、事务和发布/订阅等特性，使其成为一个功能强大的缓存、数据库和消息队列解决方案。 Redis 4.0.14是Redis 4.0版本系列的一个补丁版本，它修复了一些 bug 和安全问题，并提供了一些改进和优化。如果你有关于Redis 4.0.14的具体问题或需要更多信息，请告诉我。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值