2019-04-11笔记—Redis集群

最新推荐文章于 2024-07-24 15:17:15 发布
最新推荐文章于 2024-07-24 15:17:15 发布
阅读量237 收藏 1
点赞数 1
分类专栏： linux学习笔记
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/ai_benwoniu/article/details/89211433
版权
Redis Cluster介绍

Redis Cluster为Redis官方提供的一种分布式集群解决方案。它支持在线节点增加和减少。 集群中的节点角色可能是主，也可能是从，但需要保证每个主节点都要有对应的从节点， 这样保证了其高可用。

Redis Cluster采用了分布式系统的分片（分区）的思路，每个主节点为一个分片，这样也就意味着 存储的数据是分散在所有分片中的。当增加节点或删除主节点时，原存储在某个主节点中的数据 会自动再次分配到其他主节点。

在这里插入图片描述

如图，各节点间是相互通信的，通信端口为各节点Redis服务端口+10000，这个端口是固定的，所以注意防火墙设置。 节点之间通过二进制协议通信，这样的目的是减少带宽消耗。

在Redis Cluster中有一个概念slot，我们翻译为槽。Slot数量是固定的，为16384个。这些slot会均匀地分布到各个 节点上。另外Redis的键和值会根据hash算法存储在对应的slot中。简单讲，对于一个键值对，存的时候在哪里是通过 hash算法算出来的，那么取得时候也会算一下，知道值在哪个slot上。根据slot编号再到对应的节点上去取。

Redis Cluster无法保证数据的强一致性，这是因为当数据存储时，只要在主节点上存好了，就会告诉客户端存好了， 如果等所有从节点上都同步完再跟客户端确认，那么会有很大的延迟，这个对于客户端来讲是无法容忍的。所以， 最终Redis Cluster只好放弃了数据强一致性，而把性能放在了首位。

Redis Cluster搭建

Redis Cluster至少需要三个节点，即一主二从，本实验中使用6个节点搭建，规划如下：

主机名IP:Port角色
linux2019_1192.168.85.129:6379Redis Master
linux2019_2192.168.85.130:6379Redis Master
linux2019_3192.168.85.128:6379Redis Master
linux2019_1192.168.85.129:6380Redis slave
linux2019_2192.168.85.130:6380Redis slave
linux2019_3192.168.85.128:6380Redis slave
  1. 安装部署redis
[root@linux2019_01 ~]# vim /etc/redis_6379.conf
bind 192.168.85.129
port 6379  
daemonize yes
pidfile /var/run/redis_6379.pid 
dir /var/redis_6379
appendonly yes 
#开启集群
cluster-enabled yes  
#集群的配置文件，首次启动会自动创建
cluster-config-file nodes-6379.conf  
#集群节点连接超时时间，15秒
cluster-node-timeout 15000 

[root@linux2019_01 ~]# vim /etc/redis_6380.conf
bind 192.168.85.129
port 6380  
daemonize yes
pidfile /var/run/redis_6380.pid 
dir /var/redis_6380
appendonly yes 
#开启集群
cluster-enabled yes  
#集群的配置文件，首次启动会自动创建
cluster-config-file nodes-6380.conf  
#集群节点连接超时时间，15秒
cluster-node-timeout 15000

其他两台机器相同配置方法，修改对应的IP、端口；

  1. 部署Cluster
[root@linux2019_01 ~]# firewall-cmd --permanent --add-port 6379-6380/tcp
[root@linux2019_01 ~]# firewall-cmd --permanent --add-port  16379-16380/tcp
[root@linux2019_01 ~]# firewall-cmd --reload
[root@linux2019_01 ~]# redis-cli --cluster create 192.168.85.129:6379 192.168.85.129:6380 192.168.85.130:6379 192.168.85.130:6380 192.168.85.128:6379 192.168.85.128:6380 --cluster-replicas 1    # --cluster-replicas 1表示每个主对应一个从，实际环境中建议一个主分配2个以上的从
>>> Performing hash slots allocation on 6 nodes...
Master[0] -> Slots 0 - 5460
Master[1] -> Slots 5461 - 10922
Master[2] -> Slots 10923 - 16383
Adding replica 192.168.85.130:6380 to 192.168.85.129:6379
Adding replica 192.168.85.128:6380 to 192.168.85.130:6379
Adding replica 192.168.85.129:6380 to 192.168.85.128:6379
M: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202 192.168.85.129:6379
   slots:[0-5460] (5461 slots) master
S: 863662b3ce6262ac13cab2ac0dda0a064d012310 192.168.85.129:6380
   replicates 04c36ee67da93e57d57a5a70c3ad6d2272a5f457
M: 41304e7b210c24a638098900bf9111e71e01f211 192.168.85.130:6379
   slots:[5461-10922] (5462 slots) master
S: 973c8a8e652018cbba4272e38821be5d6b350e66 192.168.85.130:6380
   replicates 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
M: 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 192.168.85.128:6379
   slots:[10923-16383] (5461 slots) master
S: f099fa35151385a290ba09a5bd83c41c6314288d 192.168.85.128:6380
   replicates 41304e7b210c24a638098900bf9111e71e01f211
Can I set the above configuration? (type 'yes' to accept): yes
>>> Nodes configuration updated
>>> Assign a different config epoch to each node
>>> Sending CLUSTER MEET messages to join the cluster
Waiting for the cluster to join
.....
>>> Performing Cluster Check (using node 192.168.85.129:6379)
M: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202 192.168.85.129:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 973c8a8e652018cbba4272e38821be5d6b350e66 192.168.85.130:6380
   slots: (0 slots) slave
   replicates 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
S: 863662b3ce6262ac13cab2ac0dda0a064d012310 192.168.85.129:6380
   slots: (0 slots) slave
   replicates 04c36ee67da93e57d57a5a70c3ad6d2272a5f457
M: 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 192.168.85.128:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
S: f099fa35151385a290ba09a5bd83c41c6314288d 192.168.85.128:6380
   slots: (0 slots) slave
   replicates 41304e7b210c24a638098900bf9111e71e01f211
M: 41304e7b210c24a638098900bf9111e71e01f211 192.168.85.130:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
  1. 连接集群
[root@linux2019_01 ~]# redis-cli -c  -h 192.168.85.129 -p 6379
192.168.85.129:6379> keys *
(empty list or set)
192.168.85.129:6379> set k1 abc
-> Redirected to slot [12706] located at 192.168.85.128:6379
OK
192.168.85.128:6379> set k2 123bac
-> Redirected to slot [449] located at 192.168.85.129:6379
OK
192.168.85.129:6379> set m1 duan
-> Redirected to slot [6916] located at 192.168.85.130:6379
OK
192.168.85.130:6379> set m2 xiu
-> Redirected to slot [11111] located at 192.168.85.128:6379
OK
192.168.85.128:6379> set m3 guo
OK
192.168.85.128:6379> keys * #存储键值的时候由集群分配将数据存储到各个节点上
1) "m2"
2) "k1"
3) "m3"
192.168.85.128:6379> get k1
"abc"
192.168.85.128:6379> get k2
-> Redirected to slot [449] located at 192.168.85.129:6379
"123bac"
192.168.85.129:6379> get m1
-> Redirected to slot [6916] located at 192.168.85.130:6379
"duan"
192.168.85.130:6379> get m2
-> Redirected to slot [11111] located at 192.168.85.128:6379
"xiu"
192.168.85.128:6379> get m3
"guo"

再次查看集群各个节点对应的keys数量已发生变化

[root@linux2019_03 ~]# redis-cli  --cluster  check 192.168.85.128 6379
192.168.85.128:6379 (04c36ee6...) -> 3 keys | 5461 slots | 1 slaves.
192.168.85.129:6379 (7ac660a2...) -> 1 keys | 5461 slots | 1 slaves.
192.168.85.130:6379 (41304e7b...) -> 1 keys | 5462 slots | 1 slaves.
[OK] 5 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.85.128:6379)
M: 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 192.168.85.128:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
M: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202 192.168.85.129:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 863662b3ce6262ac13cab2ac0dda0a064d012310 192.168.85.129:6380
   slots: (0 slots) slave
   replicates 04c36ee67da93e57d57a5a70c3ad6d2272a5f457
S: 973c8a8e652018cbba4272e38821be5d6b350e66 192.168.85.130:6380
   slots: (0 slots) slave
   replicates 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
S: f099fa35151385a290ba09a5bd83c41c6314288d 192.168.85.128:6380
   slots: (0 slots) slave
   replicates 41304e7b210c24a638098900bf9111e71e01f211
M: 41304e7b210c24a638098900bf9111e71e01f211 192.168.85.130:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
  1. 集群管理
  • 查看集群情况（可以在任意一个节点上，指定任意一个节点查看集群的情况）
[root@linux2019_01 ~]# redis-cli  --cluster check 192.168.85.128:6379
192.168.85.128:6379 (04c36ee6...) -> 0 keys | 5461 slots | 1 slaves.
192.168.85.129:6379 (7ac660a2...) -> 0 keys | 5461 slots | 1 slaves.
192.168.85.130:6379 (41304e7b...) -> 0 keys | 5462 slots | 1 slaves.
[OK] 0 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.85.128:6379)
M: 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 192.168.85.128:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
M: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202 192.168.85.129:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 863662b3ce6262ac13cab2ac0dda0a064d012310 192.168.85.129:6380
   slots: (0 slots) slave
   replicates 04c36ee67da93e57d57a5a70c3ad6d2272a5f457
S: 973c8a8e652018cbba4272e38821be5d6b350e66 192.168.85.130:6380
   slots: (0 slots) slave
   replicates 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
S: f099fa35151385a290ba09a5bd83c41c6314288d 192.168.85.128:6380
   slots: (0 slots) slave
   replicates 41304e7b210c24a638098900bf9111e71e01f211
M: 41304e7b210c24a638098900bf9111e71e01f211 192.168.85.130:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
  • 在线迁移槽
[root@linux2019_02 ~]# redis-cli  --cluster  reshard   192.168.85.128 6379 
>>> Performing Cluster Check (using node 192.168.85.128:6379)
M: 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 192.168.85.128:6379
   slots:[11923-16383] (4461 slots) master
   1 additional replica(s)
M: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202 192.168.85.129:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 863662b3ce6262ac13cab2ac0dda0a064d012310 192.168.85.129:6380
   slots: (0 slots) slave
   replicates 04c36ee67da93e57d57a5a70c3ad6d2272a5f457
S: 973c8a8e652018cbba4272e38821be5d6b350e66 192.168.85.130:6380
   slots: (0 slots) slave
   replicates 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
S: f099fa35151385a290ba09a5bd83c41c6314288d 192.168.85.128:6380
   slots: (0 slots) slave
   replicates 41304e7b210c24a638098900bf9111e71e01f211
M: 41304e7b210c24a638098900bf9111e71e01f211 192.168.85.130:6379
   slots:[5461-11922] (6462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
How many slots do you want to move (from 1 to 16384)? 20    #指定需要迁移槽的数量
What is the receiving node ID? 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 #指定接收槽的节点ID
Please enter all the source node IDs.
  Type 'all' to use all the nodes as source nodes for the hash slots.
  Type 'done' once you entered all the source nodes IDs.
Source node #1: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
Source node #2: done

Ready to move 20 slots.
  Source nodes:
    M: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202 192.168.85.129:6379
       slots:[0-5460] (5461 slots) master
       1 additional replica(s)
  Destination node:
    M: 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 192.168.85.128:6379
       slots:[11923-16383] (4461 slots) master
       1 additional replica(s)
  Resharding plan:
    Moving slot 0 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 1 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 2 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 3 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 4 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 5 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 6 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 7 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 8 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 9 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 10 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 11 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 12 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 13 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 14 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 15 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 16 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 17 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 18 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
    Moving slot 19 from 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
Do you want to proceed with the proposed reshard plan (yes/no)? yes
Moving slot 0 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 1 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 2 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 3 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 4 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 5 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 6 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 7 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 8 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 9 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 10 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 11 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 12 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 13 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 14 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 15 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 16 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 17 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 18 from 192.168.85.129:6379 to 192.168.85.128:6379: 
Moving slot 19 from 192.168.85.129:6379 to 192.168.85.128:6379: 
[root@linux2019_02 ~]# redis-cli  --cluster  check 192.168.85.128 6379  #查看迁移后的集群节点情况
192.168.85.128:6379 (04c36ee6...) -> 2 keys | 4481 slots | 1 slaves.
192.168.85.129:6379 (7ac660a2...) -> 1 keys | 5441 slots | 1 slaves.
192.168.85.130:6379 (41304e7b...) -> 2 keys | 6462 slots | 1 slaves.
[OK] 5 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.85.128:6379)
M: 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 192.168.85.128:6379
   slots:[0-19],[11923-16383] (4481 slots) master
   1 additional replica(s)
M: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202 192.168.85.129:6379
   slots:[20-5460] (5441 slots) master
   1 additional replica(s)
S: 863662b3ce6262ac13cab2ac0dda0a064d012310 192.168.85.129:6380
   slots: (0 slots) slave
   replicates 04c36ee67da93e57d57a5a70c3ad6d2272a5f457
S: 973c8a8e652018cbba4272e38821be5d6b350e66 192.168.85.130:6380
   slots: (0 slots) slave
   replicates 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
S: f099fa35151385a290ba09a5bd83c41c6314288d 192.168.85.128:6380
   slots: (0 slots) slave
   replicates 41304e7b210c24a638098900bf9111e71e01f211
M: 41304e7b210c24a638098900bf9111e71e01f211 192.168.85.130:6379
   slots:[5461-11922] (6462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
  • 平衡各节点槽数量
[root@linux2019_02 ~]# redis-cli --cluster rebalance --cluster-threshold 1 192.168.85.128:6379
>>> Performing Cluster Check (using node 192.168.85.128:6379)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Rebalancing across 3 nodes. Total weight = 3.00
Moving 981 slots from 192.168.85.130:6379 to 192.168.85.128:6379
#####################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################
Moving 20 slots from 192.168.85.130:6379 to 192.168.85.129:6379
####################
[root@linux2019_02 ~]# redis-cli --cluster check 192.168.85.128 6379
192.168.85.128:6379 (04c36ee6...) -> 2 keys | 5462 slots | 1 slaves.
192.168.85.129:6379 (7ac660a2...) -> 1 keys | 5461 slots | 1 slaves.
192.168.85.130:6379 (41304e7b...) -> 2 keys | 5461 slots | 1 slaves.
[OK] 5 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.85.128:6379)
M: 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 192.168.85.128:6379
   slots:[0-19],[5461-6441],[11923-16383] (5462 slots) master
   1 additional replica(s)
M: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202 192.168.85.129:6379
   slots:[20-5460],[6442-6461] (5461 slots) master
   1 additional replica(s)
S: 863662b3ce6262ac13cab2ac0dda0a064d012310 192.168.85.129:6380
   slots: (0 slots) slave
   replicates 04c36ee67da93e57d57a5a70c3ad6d2272a5f457
S: 973c8a8e652018cbba4272e38821be5d6b350e66 192.168.85.130:6380
   slots: (0 slots) slave
   replicates 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
S: f099fa35151385a290ba09a5bd83c41c6314288d 192.168.85.128:6380
   slots: (0 slots) slave
   replicates 41304e7b210c24a638098900bf9111e71e01f211
M: 41304e7b210c24a638098900bf9111e71e01f211 192.168.85.130:6379
   slots:[6462-11922] (5461 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
  • 删除集群节点
[root@linux2019_03 ~]# redis-cli --cluster del-node 192.168.85.130:6380 973c8a8e652018cbba4272e38821be5d6b350e66
>>> Removing node 973c8a8e652018cbba4272e38821be5d6b350e66 from cluster 192.168.85.130:6380
>>> Sending CLUSTER FORGET messages to the cluster...
>>> SHUTDOWN the node.
[root@linux2019_03 ~]# redis-cli --cluster check 192.168.85.129 6379
192.168.85.129:6379 (7ac660a2...) -> 1 keys | 5461 slots | 0 slaves.
192.168.85.128:6379 (04c36ee6...) -> 2 keys | 5462 slots | 1 slaves.
192.168.85.130:6379 (41304e7b...) -> 2 keys | 5461 slots | 1 slaves.
[OK] 5 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.85.129:6379)
M: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202 192.168.85.129:6379
   slots:[20-5460],[6442-6461] (5461 slots) master
S: 863662b3ce6262ac13cab2ac0dda0a064d012310 192.168.85.129:6380
   slots: (0 slots) slave
   replicates 04c36ee67da93e57d57a5a70c3ad6d2272a5f457
M: 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 192.168.85.128:6379
   slots:[0-19],[5461-6441],[11923-16383] (5462 slots) master
   1 additional replica(s)
S: f099fa35151385a290ba09a5bd83c41c6314288d 192.168.85.128:6380
   slots: (0 slots) slave
   replicates 41304e7b210c24a638098900bf9111e71e01f211
M: 41304e7b210c24a638098900bf9111e71e01f211 192.168.85.130:6379
   slots:[6462-11922] (5461 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
  • 添加集群节点
[root@linux2019_03 ~]# redis-cli --cluster add-node 192.168.85.130:6382 192.168.85.129:6379 --cluster-slave --cluster-master-id 68753f15439d1fc496f320999560e217b1a31baa
#后面不带参数，添加的节点为主
#--cluster-slave  这样添加的节点为从
#--cluster-slave --cluster-master-id  添加从并指定主
>>> Adding node 192.168.85.130:6382 to cluster 192.168.85.129:6379
>>> Performing Cluster Check (using node 192.168.85.129:6379)
M: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202 192.168.85.129:6379
   slots:[20-5460],[6442-6461] (5461 slots) master
   1 additional replica(s)
S: 973c8a8e652018cbba4272e38821be5d6b350e66 192.168.85.130:6380
   slots: (0 slots) slave
   replicates 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
S: 863662b3ce6262ac13cab2ac0dda0a064d012310 192.168.85.129:6380
   slots: (0 slots) slave
   replicates 04c36ee67da93e57d57a5a70c3ad6d2272a5f457
M: 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 192.168.85.128:6379
   slots:[0-19],[5461-6441],[11923-16383] (5462 slots) master
   1 additional replica(s)
M: 68753f15439d1fc496f320999560e217b1a31baa 192.168.85.130:6381
   slots: (0 slots) master
S: f099fa35151385a290ba09a5bd83c41c6314288d 192.168.85.128:6380
   slots: (0 slots) slave
   replicates 41304e7b210c24a638098900bf9111e71e01f211
M: 41304e7b210c24a638098900bf9111e71e01f211 192.168.85.130:6379
   slots:[6462-11922] (5461 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 192.168.85.130:6382 to make it join the cluster.
Waiting for the cluster to join
...
>>> Configure node as replica of 192.168.85.130:6381.
[OK] New node added correctly.
[root@linux2019_03 ~]# 
[root@linux2019_03 ~]# redis-cli --cluster check 192.168.85.129 6379
192.168.85.129:6379 (7ac660a2...) -> 0 keys | 5461 slots | 1 slaves.
192.168.85.128:6379 (04c36ee6...) -> 2 keys | 5462 slots | 1 slaves.
192.168.85.130:6381 (68753f15...) -> 0 keys | 0 slots | 1 slaves.
192.168.85.130:6379 (41304e7b...) -> 2 keys | 5461 slots | 1 slaves.
[OK] 4 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.85.129:6379)
M: 7ac660a2444df7f3e29ab59ac9e1044b0dedd202 192.168.85.129:6379
   slots:[20-5460],[6442-6461] (5461 slots) master
   1 additional replica(s)
S: 973c8a8e652018cbba4272e38821be5d6b350e66 192.168.85.130:6380
   slots: (0 slots) slave
   replicates 7ac660a2444df7f3e29ab59ac9e1044b0dedd202
S: 863662b3ce6262ac13cab2ac0dda0a064d012310 192.168.85.129:6380
   slots: (0 slots) slave
   replicates 04c36ee67da93e57d57a5a70c3ad6d2272a5f457
M: 04c36ee67da93e57d57a5a70c3ad6d2272a5f457 192.168.85.128:6379
   slots:[0-19],[5461-6441],[11923-16383] (5462 slots) master
   1 additional replica(s)
M: 68753f15439d1fc496f320999560e217b1a31baa 192.168.85.130:6381
   slots: (0 slots) master
   1 additional replica(s)
S: f099fa35151385a290ba09a5bd83c41c6314288d 192.168.85.128:6380
   slots: (0 slots) slave
   replicates 41304e7b210c24a638098900bf9111e71e01f211
S: 56adc709f69b47492852cc322f9ef9d40d257ba8 192.168.85.130:6382
   slots: (0 slots) slave
   replicates 68753f15439d1fc496f320999560e217b1a31baa
M: 41304e7b210c24a638098900bf9111e71e01f211 192.168.85.130:6379
   slots:[6462-11922] (5461 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

  • 修复参数#redis-cli --cluster fix 192.168.85.129 6379

  • 将集群外部redis实例中的数据导入到集群中去

ai_benwoniu
关注
专栏目录
Redis集群形式--哨兵模式集群和高可用模式集群---Redis学习笔记003
添柴程序猿的专栏
06-08 298
对于redis集群,我们搭建的时候可以选择两种模式:这里记录一下,至于如何搭建,网上教程太多了,这里不多说了,记录一下到时候用到时候,可以想到应该使用哪种模式,到时候去搭建就可以了哨兵模式的集群:在redis3.0以前的版本要实现集群一般是借助哨兵sentinel工具来监控master节点的状态，如果master节点异常，则会做主从切换，将某一台slave作为master，哨兵的配置略微复杂，并且性能和高可用性等各方面表现一般，特别是在主从切换的瞬间存在访问瞬断的情况，而且哨兵模式只有一个主节点对外提供服务
redis5 集群安装--redis-cluster命令使用（笔记）
灰猫
05-27 1132
准备 somaxconn参数 对于一个TCP连接，Server与Client需要通过三次握手来建立网络连接.当三次握手成功后, 连接队列上限。 系统中每一个端口最大的监听队列的长度,这是个全局的参数,默认值为128,具体信息为。 修改 # 重启后就没有了 echo 2048 > /proc/sys/net/core/somaxconn vim /etc/sysctl.conf # 在/etc/sysctl.conf中添加如下 net.core.somaxconn = 2048 安装
11_Redis集群
weixin_30732487的博客
05-19 64
【Redis集群分类】 1.主从复制（master/slave） 2.高可用Sentinel哨兵 3.高可用集群模式 【 主从复制（master/slave）】 [Redis一主多从架构] 通过持久化功能，Redis保证了即使在服务器重启的情况下也不会丢失（或少量丢失）数据，但由于数据是存储在一台服务器上的，如果这台服务器出现故障，比如硬盘坏了，也会导致数据丢失。 为了避免数据...
Redis集群：redis cluster方案
五山口老法师
01-04 208
redis集群原理之官方的Redis Cluster方案 redis是单线程，但是一般的作为缓存使用的话，redis足够了，因为它的读写速度太快了。   官方的一个简单测试： 测试完成了50个并发执行100000个请求。　　　　　 设置和获取的值是一个256字节字符串。结果:读的速度是110000次/s,写的速度是81000次/s  　　　　在这么快的读写速度下，对于一般程序来说...
redis构建集群时，一直Waiting for the cluster to join
最新发布
不做菜虚困的博客
07-24 803
但是，您可以通过阅读 Redis 集群源代码中的 cluster.h 和 cluster.c 文件来获取有关集群总线协议的更多详细信息。如果 Redis 节点正在监听端口 6379 上的客户端连接，并且您在 redis.conf 中设置 cluster-port 20000，则将打开集群总线端口 20000。如果 Redis 节点正在监听端口 6379 上的客户端连接，并且您未在 redis.conf 中添加 cluster-port 参数，则将打开集群总线端口 16379。但是出现上面的情况。
【Redis源码】集群之主从复制replication（十）
c-rain
02-23 510
前言： 说到主从大家应该都不陌生，也应该都清楚主从解决服务的哪些问题。单台服务器的支撑能力是有限的，为了提高我们的QPS或者说数据的容灾。主从服务则起到了相应的作用。 不过主从复制也会有一些缺点，比如说“高可用问题”，“单服务器资源有限问题”。针对高可用问题我们后续解析redis集群的哨兵，针对单服务器问题，我们会解析redis Cluster分布式应用。 redis版本： 4.0.0 ...
在docker中部署redis cluster，解决Waiting for the cluster to join...问题和支持spring的访问
qq_40693970的博客
07-25 821
解决在docker中部署redis集群出现的waiting for the cluster to join问题和解决spring无法访问集群的问题
redis之复制之谜(二)
happytree001的博客
07-01 542
redis的复制第三版（异步复制） redis在2.2.0版本中引入了replica异步接收数据
Redis笔记-尚硅谷周阳V1.3-脑图
06-16
根据《Redis笔记-尚硅谷周阳V1.3》整理，脑图、思维导图xmind
cent7.3-redis集群5.0.0搭建-详细笔记文档
07-17
CentOS 7.3 上 Redis 5.0.0 集群搭建详解 在本文中，我们将详细介绍如何在 CentOS 7.3 上搭建 Redis 5.0.0 集群。该集群由 6 台机器组成，每台机器都安装了 Redis 5.0.0，并配置了集群模式。 环境准备 在开始搭建...
3-13-3-redis-随堂笔记.docx
11-26
### 13.1 Redis概述 #### 13.1.1 Redis是什么 Redis (Remote Dictionary Server) 是一种开源的键值对存储系统，最初由Salvatore Sanfilippo开发，于2009年首次发布。它不仅是一种内存中的缓存系统，还提供了持久化...
Redis源码解读（二十）——全量同步
yh88623131的博客
05-29 449
主从同步—全量同步的设计与实现
二十一:redis主从复制实现原理
勿在浮沙筑高台
11-23 392
二十一:redis主从复制实现原理 主从复制实现原理 本文使用源码redis 2.2 主从结构有两种结构： 1.一主多从 2. 级联结果 复制方式分为： 1.全量复制 2. 增量同步 全量复制： 发生在slave初始阶段及slave断线重新连接到master 增量同步： 当全量复制完成后，主服务每执行一个写命令就会向从服务发送命令。 全量复制 1.当slave启动连接到master发送sync命令 2.master接收到sync后，开始执行bgsave命令生成RDB 3.master后续写入命令存入到
创建Redis分片集群时，Waiting for the cluster to join卡住
weixin_43378573的博客
12-06 1013
创建Redis分片集群时，Waiting for the cluster to join卡住很久无反应。
Redis集群一直Waiting for the cluster to join....的终极解决方案
weixin_43410934的博客
10-09 4527
最近在进行redis集群的时候遇到一个问题 如下图 一直提示Waiting for the cluster to join… 这里直接ctrl+c了 解决方案： 1：打开所有节点的redis.conf 配置bind属性 值是服务器的外网IP 如：bind 192.168.46.133 2：使用redis desktop Manager连接所有节点 调出命令窗口输入一下 命令 flushall c...
Redis集群安装笔记-哨兵模式配置要点简述
本文主要介绍了Redis集群的安装和配置过程，并重点介绍了Redis哨兵模式。哨兵模式下，Redis节点需要有3台机器，包括3台Redis服务器和3台Redis哨兵。在安装过程中，首先对三台机器进行Redis的单机安装，并按照以下...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值