做网站先做ue心理软件定制开发

• 集群节点信息
• 这时候停掉一个master 172.30.60.31
  • 从集群信息集中我们可以看到172.30.60.31的slave是172.30.60.41，查看41的日志，发现他成为了新的master
• 这时候我们在将172.30.60.41也杀死，会发现集群异常了
  • 尝试把172.30.60.31启动，发现集群还是异常的，因为联系不到他的master，查看31的日志
  • 我们尝试手动把172.30.60.31升级为master
  • 因为联系不到master，直接强制升级
  • 查看集群状态，发现恢复正常了
• 当集群中一个master和他的slave都挂了的情况下(因测试主从发生了变化，不用在意)，集群异常
  • 假如这两个节点都无法启动了，这时候应该怎么办？尝试把172.30.60.41从节点升级为主
  • 首先把172.30.60.41设置为172.30.60.31的从节点: 

    redis-cli -p 7000 -h 172.30.60.41 cluster replicate 714bae586a45160a4d6869e4547b4aca0361fd0e

  • 
  • 然后升级172.30.60.41升级为主节点，然后查看集群状态,恢复正常了
• 也可以新增一个节点到集群中 172.30.100.114 7777

redis-cli -p 7000 cluster meet 172.30.100.114 7000

# 因为挂掉的master slots是5461-10922，所以这里指定5461

redis-cli -p 7777 -h 172.30.100.114 CLUSTER ADDSLOTS 5461

redis-cli -p 7777 -h 172.30.100.114

# 强制升级为主节点

cluster failover force

# 查看集群状态

172.30.100.114:7777> cluster nodes

8104a927a687e932b906855a83c8ffee7d746798 172.30.100.114:7777@17777 myself,master - 0 1739526224000 33 connected 5461-10922

8a35a0bdfa37946b2cf9e5b1813360451f004b81 172.30.60.61:7000@17000 slave,fail - 1739525460865 0 0 disconnected

3a84c93ed5bcbf67a1ec746501e6574c736e525d 172.30.60.21:7000@17000 master - 0 1739526225404 17 connected 10923-16383

7fa07aae1f0ecaeee805a578cadd52184f6214a3 172.30.60.11:7000@17000 master - 0 1739526227000 13 connected 0-5460

f198e3277009f6dbbf0899bd26c9954cc15b977c 172.30.60.51:7000@17000 slave 3a84c93ed5bcbf67a1ec746501e6574c736e525d 0 1739526227416 17 connected

714bae586a45160a4d6869e4547b4aca0361fd0e 172.30.60.31:7000@17000 master,fail - 1739525459356 0 32 disconnected

e509a47a20eedc0e9a9a417d203dbf3161ce8041 172.30.60.41:7000@17000 slave 7fa07aae1f0ecaeee805a578cadd52184f6214a3 0 1739526225000 13 connected

172.30.100.114:7777> cluster info

cluster_state:ok

cluster_slots_assigned:16384

cluster_slots_ok:16384

cluster_slots_pfail:0

cluster_slots_fail:0

cluster_known_nodes:7

cluster_size:3

cluster_current_epoch:33

cluster_my_epoch:33

cluster_stats_messages_ping_sent:771

cluster_stats_messages_pong_sent:764

cluster_stats_messages_auth-req_sent:6

cluster_stats_messages_sent:1541

cluster_stats_messages_ping_received:759

cluster_stats_messages_pong_received:769

cluster_stats_messages_meet_received:1

cluster_stats_messages_auth-ack_received:2

cluster_stats_messages_update_received:1

cluster_stats_messages_received:1532