变更需求为：

1、调整主从关系，所有节点都调整到10.129.51.30机器上

2、停掉10.128.51.14上的所有redis，14机器关机

  14机器下线迁移至新机房，这段时间将不能提供服务.

当前集群情况

1、一共是2台12个实例，6主6从，每台6个实例。

2、30上有3台master，没有分配槽位，需变更为从节点。
3、10.128.51.14 放在A机房，10.129.51.30放在B机房。
4、目前经过上一次的调整，把0-16383槽位从10.128.51.14都迁移到了10.129.51.30的新伪集群中。

//查看集群主从节点信息。进行分析

[root@ht20 redis]# ./redis-cli -c -h 10.129.51.30 -p 7736   //输出结果我进行了小范围的调整

10.129.51.30:7736> cluster nodes
//6台从,每2台从同步一个master,黄色代表对应。
4bee54a5049524a6280fdb8a8de00a5bb94ccaa1 10.128.51.14:7733@17733 slave d1c7d99e13a2d7317baf883dffa906470a606641 0 1646269992000 62 connected

07c99eae8176eb0e985c5a9914f42900d18fb39b 10.128.51.14:7736@17736 slave d1c7d99e13a2d7317baf883dffa906470a606641 0 1646269990000 62 connected

fb28e95eb37b8d827c0f48800c4d08e64c6fc335 10.128.51.14:7731@17731 slave d46f032ea50763de8353fd530535412df6ffdc00 0 1646269993529 60 connected

ff34a5fadf42078332445bcf41a2b59416fd92da 10.128.51.14:7734@17734 slave d46f032ea50763de8353fd530535412df6ffdc00 0 1646269992327 60 connected

41767372c36cc268872e86d96660a32bf540624f 10.128.51.14:7732@17732 slave 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 0 1646269990324 63 connected

b9a55f739a65e6277e40cdbb806b5443c8aad66e 10.128.51.14:7735@17735 slave 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 0 1646269994330 63 connected


//闲置

27f7e8dede5b68581486ce8cefdd656032baed70 10.129.51.30:7734@17734 master - 0 1646269994826 4 connected

32ee19af1f6a534c4014b9c41d387666f049354b 10.129.51.30:7735@17735 master - 0 1646269989315 0 connected

bc5051aef1a756c274907d23198fbb932c384151 10.129.51.30:7736@17736 myself,master - 0 1646269991000 6 connected

//带槽位的master

d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731@17731 master - 0 1646269995327 60 connected 0-5460

91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732@17732 master - 0 1646269993324 63 connected 5461-10922

d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733@17733 master - 0 1646269994000 62 connected 10923-16383

我们继续分析，我把主要信息调整了一下，删除掉了防碍分析的信息。只保留相互之间关系(黄色做为示例，标记了相互关系)

10.129.51.30:7736> cluster nodes

1、10.129.51.30:7731 主 0-5460, master标记 d46f032ea50763de8353fd530535412df6ffdc00 的两个从节点

fb28e95eb37b8d827c0f48800c4d08e64c6fc335 10.128.51.14:7731  slave d46f032ea50763de8353fd530535412df6ffdc00

ff34a5fadf42078332445bcf41a2b59416fd92da 10.128.51.14:7734  slave d46f032ea50763de8353fd530535412df6ffdc00  

2、10.129.51.30:7732 主 5461-10922, master标记 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 的两个从节点

41767372c36cc268872e86d96660a32bf540624f 10.128.51.14:7732  slave 91b7f8c79c91c7edd77458c332f0b9299bdb94d4

b9a55f739a65e6277e40cdbb806b5443c8aad66e 10.128.51.14:7735  slave 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 

3、10.129.51.30:7733 主 10923-16383, master标记 d1c7d99e13a2d7317baf883dffa906470a606641 的两个从节点

4bee54a5049524a6280fdb8a8de00a5bb94ccaa1 10.128.51.14:7733 slave d1c7d99e13a2d7317baf883dffa906470a606641

07c99eae8176eb0e985c5a9914f42900d18fb39b 10.128.51.14:7736 slave d1c7d99e13a2d7317baf883dffa906470a606641

//以上6台主机全部要关机

//master，这几台不变

d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731 master  0-5460

91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732 master  5461-10922

d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733 master  10923-16383

//需要等待调整为具有槽位主节点变成slave

27f7e8dede5b68581486ce8cefdd656032baed70 10.129.51.30:7734@17734 master -

32ee19af1f6a534c4014b9c41d387666f049354b 10.129.51.30:7735@17735 master -

bc5051aef1a756c274907d23198fbb932c384151 10.129.51.30:7736@17736 myself,master

根据第二次整理，我再次整理出相互关系表格，方便我下面实际操作。

主节点ID                                   主节点地址          从节点ID                                 从节点地址

//主槽位 0-5460

d46f032ea50763de8353fd530535412df6ffdc00  10.129.51.30:7731 fb28e95eb37b8d827c0f48800c4d08e64c6fc335 10.128.51.14:7731

d46f032ea50763de8353fd530535412df6ffdc00  10.129.51.30:7731 ff34a5fadf42078332445bcf41a2b59416fd92da 10.128.51.14:7734

//主槽位 5461-10922

91b7f8c79c91c7edd77458c332f0b9299bdb94d4  10.129.51.30:7732 41767372c36cc268872e86d96660a32bf540624f 10.128.51.14:7732

91b7f8c79c91c7edd77458c332f0b9299bdb94d4  10.129.51.30:7732 b9a55f739a65e6277e40cdbb806b5443c8aad66e 10.128.51.14:7735

//主槽位 10923-16383

d1c7d99e13a2d7317baf883dffa906470a606641  10.129.51.30:7733 4bee54a5049524a6280fdb8a8de00a5bb94ccaa1 10.128.51.14:7733

d1c7d99e13a2d7317baf883dffa906470a606641  10.129.51.30:7733 07c99eae8176eb0e985c5a9914f42900d18fb39b 10.128.51.14:7736

看到以上的信息，基本就已经很明确，redis集群中相互之间的关系，以及迁移动机和实际要达成的目标。

要达成目标为:

1、10.128.51.14:7731和10.128.51.14:7734 删除

2、10.129.51.30:7734从集群中移除 （原来不带槽位的master）

3、把10.129.51.30:7734节点，重新配置后，设置为当前集群中的10.129.51.30:7731主节点的从节点。

实际迁移、调整操作

一、设置新的主从关系（7734->7731）
1、删除从节点，在任意一台服务器上执行下面命令：
//操作1.删除从节点10.128.51.14:7734

[root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7731 ff34a5fadf42078332445bcf41a2b59416fd92da

>>> Removing node ff34a5fadf42078332445bcf41a2b59416fd92da from cluster 10.129.51.30:7731

>>> Sending CLUSTER FORGET messages to the cluster...

>>> SHUTDOWN the node.

//我们到另一台14机器上查下，已经被杀掉，也没有在cluster nodes里面出现.

//操作2.删除从节点 10.128.51.14:7731

[root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7731 fb28e95eb37b8d827c0f48800c4d08e64c6fc335

>>> Removing node fb28e95eb37b8d827c0f48800c4d08e64c6fc335 from cluster 10.129.51.30:7731

>>> Sending CLUSTER FORGET messages to the cluster...

>>> SHUTDOWN the node.

//我们看到10.128.51.14:7731从redis集群中被删除，并不会杀死该实例

解释:
a、删掉 10.129.51.30:7731 的两个从节点 10.128.51.14:7731 和 10.128.51.14:7734

b、解释 10.129.51.30:7731 为主节点地址， fb28e95eb37b8d827c0f48800c4d08e64c6fc335 为 10.128.51.14:7731 从节点标记

c、解释 10.129.51.30:7731 为主节点地址， ff34a5fadf42078332445bcf41a2b59416fd92da 为 10.128.51.14:7734 从节点标记

  从节点断开主从关系后并不会抛弃原有数据，只是无法再获取主节点上的数据变化:

2、把10.129.51.30:7734从集群中移除 （准备把该节点作为10.129.51.30：7731的从节点）

 语法: /redis-trib.rb del-node ip:端口号 节点id

[root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7734 d46f032ea50763de8353fd530535412df6ffdc00

[root@ht20 redis]# ps -ef | grep redis
 root 40843 126564 0 12:34 pts/0 00:00:00 grep --color=auto redis
 root 57063 1 0 Mar01 ? 00:03:53 /data/redis_fpmai1/redis/redis-server 10.129.51.30:7731 [cluster]
 root 58394 1 0 Mar01 ? 00:03:25 /data/redis_fpmai2/redis/redis-server 10.129.51.30:7732 [cluster]
 root 58881 1 0 Mar01 ? 00:07:27 /data/redis_fpmai3/redis/redis-server 10.129.51.30:7733 [cluster]
 root 58893 1 0 Mar01 ? 00:03:03 /data/redis_fpmai4/redis/redis-server 10.129.51.30:7734 [cluster]
 root 58939 1 0 Mar01 ? 00:02:54 /data/redis_fpmai6/redis/redis-server 10.129.51.30:7736 [cluster]
 root 100693 1 0 Mar01 ? 00:02:45 /data/redis_fpmai5/redis/redis-server 10.129.51.30:7735 [cluster]
 //我们看到10.128.51.14:7734 master从redis集群中被删除，并不会杀死该实例,不过还是要有几步处理。
 //a、先停掉 10.129.51.30:7734 ,删除data里面的内容，否则添加主从关系会提示不成功node not empty。
  [root@ht20 redis]# kill -9 58893 //7734进程id
 //b、因为以前已经加入过集群，删除其中的信息
  [root@ht20 redis]#rm -rf /data/redis_fpmai4/redis/data/*.*
 //c、重新启动7734实例
 [root@ht20 redis]# /data/redis_fpmai4/redis/redis-server /data/redis_fpmai4/redis/redis.conf

3、前面的准备工作做完之后，就可以把10.129.51.30：7731 mater上添加一个slave从节点（需要重新建立主从关系）
  语法 ./redis-trib.rb add-node --slave --master-id 主节点id 从节点地址  主节点地址

[root@ht20 redis]# ./redis-trib.rb add-node --slave --master-id d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7734 10.129.51.30:7731
>>> Adding node 10.129.51.30:7734 to cluster 10.129.51.30:7731
>>> Performing Cluster Check (using node 10.129.51.30:7731)
M: d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731
slots:0-5460 (5461 slots) master
0 additional replica(s)
M: d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733
slots:10923-16383 (5461 slots) master
2 additional replica(s)
S: 07c99eae8176eb0e985c5a9914f42900d18fb39b 10.128.51.14:7736
slots: (0 slots) slave
replicates d1c7d99e13a2d7317baf883dffa906470a606641
S: 41767372c36cc268872e86d96660a32bf540624f 10.128.51.14:7732
slots: (0 slots) slave
replicates 91b7f8c79c91c7edd77458c332f0b9299bdb94d4
M: 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732
slots:5461-10922 (5462 slots) master
2 additional replica(s)
M: 32ee19af1f6a534c4014b9c41d387666f049354b 10.129.51.30:7735
slots: (0 slots) master
0 additional replica(s)
M: bc5051aef1a756c274907d23198fbb932c384151 10.129.51.30:7736
slots: (0 slots) master
0 additional replica(s)
S: 4bee54a5049524a6280fdb8a8de00a5bb94ccaa1 10.128.51.14:7733
slots: (0 slots) slave
replicates d1c7d99e13a2d7317baf883dffa906470a606641
S: b9a55f739a65e6277e40cdbb806b5443c8aad66e 10.128.51.14:7735
slots: (0 slots) slave
replicates 91b7f8c79c91c7edd77458c332f0b9299bdb94d4
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 10.129.51.30:7734 to make it join the cluster.
Waiting for the cluster to join.
>>> Configure node as replica of 10.129.51.30:7731.
[OK] New node added correctly.

//检查加入情况，14的2个节点已经删除，30的7734已变成slave

解释：
1、d46f032ea50763de8353fd530535412df6ffdc00 master标识
2、10.129.51.30:7734 要加入的新的机器 (之前加入过，所以需要停掉该实例，删除data目录下的内容，再重新启动该实例)
3、10.129.51.30:7731 是主节点,即有槽位的机器(当然也可以是其他任意主节点，有槽位的),

 //检查下集群中是不是已经达到我们的目的(红色这一行就是我们的目标)。

[root@ht20 redis]# ./redis-cli -c -h 10.129.51.30 -p 7731
 10.129.51.30:7731> cluster nodes
 d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733@17733 master - 10923-16383
 421ccd9a53168359272b733869fcb8ad827aa655 10.129.51.30:7734@17734 slave d46f032ea50763de8353fd530535412df6ffdc00 
 d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731@17731 myself,master - 0-5460
 07c99eae8176eb0e985c5a9914f42900d18fb39b 10.128.51.14:7736@17736 slave d1c7d99e13a2d7317baf883dffa906470a606641  
 27f7e8dede5b68581486ce8cefdd656032baed70 :0@0 master,fail,noaddr  //这一条就是设置主从时候，失误导致的
 41767372c36cc268872e86d96660a32bf540624f 10.128.51.14:7732@17732 slave 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 
 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732@17732 master -  5461-10922
 32ee19af1f6a534c4014b9c41d387666f049354b 10.129.51.30:7735@17735 master -  connected
 bc5051aef1a756c274907d23198fbb932c384151 10.129.51.30:7736@17736 master -  connected
 4bee54a5049524a6280fdb8a8de00a5bb94ccaa1 10.128.51.14:7733@17733 slave d1c7d99e13a2d7317baf883dffa906470a606641  
 b9a55f739a65e6277e40cdbb806b5443c8aad66e 10.128.51.14:7735@17735 slave 91b7f8c79c91c7edd77458c332f0b9299bdb94d4

所以看到红色的关键语句就4条。

回顾下主从的关系

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

1、10.129.51.30:7731 主 0-5460, master标记 d46f032ea50763de8353fd530535412df6ffdc00 的两个从节点

fb28e95eb37b8d827c0f48800c4d08e64c6fc335 10.128.51.14:7731  slave d46f032ea50763de8353fd530535412df6ffdc00

ff34a5fadf42078332445bcf41a2b59416fd92da 10.128.51.14:7734  slave d46f032ea50763de8353fd530535412df6ffdc00  

2、10.129.51.30:7732 主 5461-10922, master标记 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 的两个从节点

41767372c36cc268872e86d96660a32bf540624f 10.128.51.14:7732  slave 91b7f8c79c91c7edd77458c332f0b9299bdb94d4

b9a55f739a65e6277e40cdbb806b5443c8aad66e 10.128.51.14:7735  slave 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 

3、10.129.51.30:7733 主 10923-16383, master标记 d1c7d99e13a2d7317baf883dffa906470a606641 的两个从节点

4bee54a5049524a6280fdb8a8de00a5bb94ccaa1 10.128.51.14:7733 slave d1c7d99e13a2d7317baf883dffa906470a606641

07c99eae8176eb0e985c5a9914f42900d18fb39b 10.128.51.14:7736 slave d1c7d99e13a2d7317baf883dffa906470a606641 

//master

d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731@17731 master - 0 1646269995327 60 connected 0-5460

91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732@17732 master - 0 1646269993324 63 connected 5461-10922

d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733@17733 master - 0 1646269994000 62 connected 10923-16383

//等待调整为slave

27f7e8dede5b68581486ce8cefdd656032baed70 10.129.51.30:7734@17734 master - 0 1646269994826 4 connected

32ee19af1f6a534c4014b9c41d387666f049354b 10.129.51.30:7735@17735 master - 0 1646269989315 0 connected

bc5051aef1a756c274907d23198fbb932c384151 10.129.51.30:7736@17736 myself,master - 0 1646269991000 6 connected

  主节点ID                                 主节点地址      从节点ID                                从节点地址

//主槽位 0-5460

d46f032ea50763de8353fd530535412df6ffdc00  10.129.51.30:7731 fb28e95eb37b8d827c0f48800c4d08e64c6fc335 10.128.51.14:7731

d46f032ea50763de8353fd530535412df6ffdc00  10.129.51.30:7731 ff34a5fadf42078332445bcf41a2b59416fd92da 10.128.51.14:7734

//主槽位 5461-10922

91b7f8c79c91c7edd77458c332f0b9299bdb94d4  10.129.51.30:7732 41767372c36cc268872e86d96660a32bf540624f 10.128.51.14:7732

91b7f8c79c91c7edd77458c332f0b9299bdb94d4  10.129.51.30:7732 b9a55f739a65e6277e40cdbb806b5443c8aad66e 10.128.51.14:7735

//主槽位 10923-16383

d1c7d99e13a2d7317baf883dffa906470a606641  10.129.51.30:7733 4bee54a5049524a6280fdb8a8de00a5bb94ccaa1 10.128.51.14:7733

d1c7d99e13a2d7317baf883dffa906470a606641  10.129.51.30:7733 07c99eae8176eb0e985c5a9914f42900d18fb39b 10.128.51.14:7736

 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

二、设置新的主从关系（7735->7732）

二、 设置新的主从关系（7735->7732）

1、从redis集群中删掉两个从节点(10.128.51.14:7732 和10.128.51.14:7735)

     在任意一台服务器上执行下面命令：

     //删除10.129.51.30:7732的从节点10.128.51.14:7735和10.128.51.14:7732

     [root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7732 41767372c36cc268872e86d96660a32bf540624f

     [root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7732 b9a55f739a65e6277e40cdbb806b5443c8aad66e

2、移除7735节点

    [root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7735 32ee19af1f6a534c4014b9c41d387666f049354b

    [root@ht20 redis]# kill -9 58894

    [root@ht20 redis]#rm -rf   /data/redis_fpmai5/redis/data/*.*

    [root@ht20 redis]# /data/redis_fpmai5/redis/redis-server /data/redis_fpmai5/redis/redis.conf

3、添加一个新的主从关系（重新建立主从关系）

 [root@ht20 redis]# ./redis-trib.rb add-node --slave --master-id 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7735 10.129.51.30:7732

三、 设置新的主从关系（7736->7733）

三、 设置新的主从关系（7736->7733）

1、从redis集群中删掉两个从节点(10.128.51.14:7733 和10.128.51.14:7736)

     在任意一台服务器上执行下面命令：

     //删除10.129.51.30:7732的从节点10.128.51.14:7733 和10.128.51.14:7736

     [root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7733 4bee54a5049524a6280fdb8a8de00a5bb94ccaa1

     [root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7733 07c99eae8176eb0e985c5a9914f42900d18fb39b

2、移除7736节点

    [root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7736  bc5051aef1a756c274907d23198fbb932c384151

    [root@ht20 redis]# kill -9 58894

    [root@ht20 redis]#rm -rf   /data/redis_fpmai5/redis/data/*.*

    [root@ht20 redis]# /data/redis_fpmai5/redis/redis-server /data/redis_fpmai5/redis/redis.conf

3、添加一个新的主从关系（重新建立主从关系）

 [root@ht20 redis]# ./redis-trib.rb add-node --slave --master-id d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7736 10.129.51.30:7733

  注意：del-node只能删除没有分配slot的节点

执行相关过程就单独放这里吧。 这样可以和上面的操作分开，上面的二和三中的操作，看着基本很简洁了，

//删除7732节点
[root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7732 41767372c36cc268872e86d96660a32bf540624f

>>> Removing node 41767372c36cc268872e86d96660a32bf540624f from cluster 10.129.51.30:7732

>>> Sending CLUSTER FORGET messages to the cluster...

>>> SHUTDOWN the node.
//删除7732从节点

[root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7732 b9a55f739a65e6277e40cdbb806b5443c8aad66e

>>> Removing node b9a55f739a65e6277e40cdbb806b5443c8aad66e from cluster 10.129.51.30:7732

>>> Sending CLUSTER FORGET messages to the cluster...

>>> SHUTDOWN the node.

//删除集群中的节点（之前是标记为了master,但是槽位是空的）

[root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7735 32ee19af1f6a534c4014b9c41d387666f049354b
>>> Removing node 32ee19af1f6a534c4014b9c41d387666f049354b from cluster 10.129.51.30:7735
>>> Sending CLUSTER FORGET messages to the cluster...
>>> SHUTDOWN the node.

//删除集群中的节点（之前标记也是master,槽位为空）

[root@ht20 redis]# ./redis-trib.rb del-node 10.129.51.30:7736 bc5051aef1a756c274907d23198fbb932c384151
>>> Removing node bc5051aef1a756c274907d23198fbb932c384151 from cluster 10.129.51.30:7736
>>> Sending CLUSTER FORGET messages to the cluster...
>>> SHUTDOWN the node.

//为确保迁移过程中正确，检查一下当前集群情况

[root@ht20 redis]# ./redis-cli -c -h 10.129.51.30 -p 7731
10.129.51.30:7731> cluster nodes
d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733 master  10923-16383
421ccd9a53168359272b733869fcb8ad827aa655 10.129.51.30:7734 slave  d46f032ea50763de8353fd530535412df6ffdc00  
d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731 myself,master 0-5460
91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732 master 5461-10922

//删除掉redis_fpmai5和redis_fpmai6的data目录下的文件，重新启动

[root@ht20 redis]# /data/redis_fpmai5/redis/redis-server /data/redis_fpmai5/redis/redis.conf
[root@ht20 redis]# /data/redis_fpmai6/redis/redis-server /data/redis_fpmai6/redis/redis.conf
[root@ht20 redis]# ps -ef | grep redis
root 42097 1 0 12:40 ? 00:00:07 /data/redis_fpmai4/redis/redis-server 10.129.51.30:7734 [cluster]
root 57063 1 0 Mar01 ? 00:04:03 /data/redis_fpmai1/redis/redis-server 10.129.51.30:7731 [cluster]
root 58394 1 0 Mar01 ? 00:03:35 /data/redis_fpmai2/redis/redis-server 10.129.51.30:7732 [cluster]
root 58881 1 0 Mar01 ? 00:07:40 /data/redis_fpmai3/redis/redis-server 10.129.51.30:7733 [cluster]
root 67736 1 0 14:35 ? 00:00:00 /data/redis_fpmai5/redis/redis-server 10.129.51.30:7735 [cluster]
root 67774 1 0 14:35 ? 00:00:00 /data/redis_fpmai6/redis/redis-server 10.129.51.30:7736 [cluster]

//执行中出现这样错误，我已经删除掉了data目录下的内容了，可能操作那块漏掉了，刚才操作有一步严谨。重新来一遍就不会出下面问题。

[root@ht20 redis]# ./redis-trib.rb add-node --slave --master-id 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7735 10.129.51.30:7732
>>> Adding node 10.129.51.30:7735 to cluster 10.129.51.30:7732
>>> Performing Cluster Check (using node 10.129.51.30:7732)
M: 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732
slots:5461-10922 (5462 slots) master
0 additional replica(s)
M: d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733
slots:10923-16383 (5461 slots) master
0 additional replica(s)
S: 421ccd9a53168359272b733869fcb8ad827aa655 10.129.51.30:7734
slots: (0 slots) slave
replicates d46f032ea50763de8353fd530535412df6ffdc00
M: d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731
slots:0-5460 (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.
[ERR] Node 10.129.51.30:7735 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0.

//我还是先杀掉7735,删除对应data目录下的文件，再重新启动7735实例，再次执行后正常

[root@ht20 redis]# /data/redis_fpmai5/redis/redis-server /data/redis_fpmai5/redis/redis.conf
[root@ht20 redis]# ./redis-trib.rb add-node --slave --master-id 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7735 10.129.51.30:7732
>>> Adding node 10.129.51.30:7735 to cluster 10.129.51.30:7732
>>> Performing Cluster Check (using node 10.129.51.30:7732)
M: 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732
slots:5461-10922 (5462 slots) master
0 additional replica(s)
M: d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733
slots:10923-16383 (5461 slots) master
0 additional replica(s)
S: 421ccd9a53168359272b733869fcb8ad827aa655 10.129.51.30:7734
slots: (0 slots) slave
replicates d46f032ea50763de8353fd530535412df6ffdc00
M: d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731
slots:0-5460 (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 10.129.51.30:7735 to make it join the cluster.
Waiting for the cluster to join..
>>> Configure node as replica of 10.129.51.30:7732.
[OK] New node added correctly.

[root@ht20 redis]# ./redis-cli -c -h 10.129.51.30 -p 7731
10.129.51.30:7731> cluster nodes
d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733@17733 master - 0 1646289642962 62 connected 10923-16383
421ccd9a53168359272b733869fcb8ad827aa655 10.129.51.30:7734@17734 slave d46f032ea50763de8353fd530535412df6ffdc00 0 1646289644000 60 connected
d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731@17731 myself,master - 0 1646289642000 60 connected 0-5460
91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732@17732 master - 0 1646289644965 63 connected 5461-10922
f0e5d3d17babbce85a9290e679a626bc0bbacc93 10.129.51.30:7735@17735 slave 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 0 1646289643963 63 connected

执行到这里，我让开发人员测试了下目前redis的情况，暂时都一切正常。 但是没有让k8s pod重新部署.

//最后执行一下

[root@ht20 redis]# ./redis-trib.rb add-node --slave --master-id d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7736 10.129.51.30:7733
>>> Adding node 10.129.51.30:7736 to cluster 10.129.51.30:7733
>>> Performing Cluster Check (using node 10.129.51.30:7733)
M: d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733
slots:10923-16383 (5461 slots) master
0 additional replica(s)
S: f0e5d3d17babbce85a9290e679a626bc0bbacc93 10.129.51.30:7735
slots: (0 slots) slave
replicates 91b7f8c79c91c7edd77458c332f0b9299bdb94d4
M: 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732
slots:5461-10922 (5462 slots) master
1 additional replica(s)
S: 421ccd9a53168359272b733869fcb8ad827aa655 10.129.51.30:7734
slots: (0 slots) slave
replicates d46f032ea50763de8353fd530535412df6ffdc00
M: d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731
slots:0-5460 (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 10.129.51.30:7736 to make it join the cluster.
Waiting for the cluster to join.
>>> Configure node as replica of 10.129.51.30:7733.
[OK] New node added correctly.

[root@ht20 redis]# ./redis-cli -c -h 10.129.51.30 -p 7731
10.129.51.30:7731> cluster nodes

//下面的关系，稍微整理了一下，如下:

d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731@17731 myself,master - 0 1646290141000 60 connected 0-5460
421ccd9a53168359272b733869fcb8ad827aa655 10.129.51.30:7734@17734 slave d46f032ea50763de8353fd530535412df6ffdc00 0 1646290140700 60 connected

91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732@17732 master - 0 1646290140000 63 connected 5461-10922
f0e5d3d17babbce85a9290e679a626bc0bbacc93 10.129.51.30:7735@17735 slave 91b7f8c79c91c7edd77458c332f0b9299bdb94d4 0 1646290141702 63 connected

d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733@17733 master - 0 1646290138698 62 connected 10923-16383
c3c7ba2d0709121e69c2881724a0c5be903a4a6a 10.129.51.30:7736@17736 slave d1c7d99e13a2d7317baf883dffa906470a606641 0 1646290142703 62 connected

迁移到此就基本结束了。 这个阶段也没有出现任何问题。

为了稳妥，让开发人员进行重新的部署。来看下pod日志打印情况和业务使用情况

d1c7d99e13a2d7317baf883dffa906470a606641 10.129.51.30:7733@17733 master 10923-16383
421ccd9a53168359272b733869fcb8ad827aa655 10.129.51.30:7734@17734 slave d46f032ea50763de8353fd530535412df6ffdc00  
d46f032ea50763de8353fd530535412df6ffdc00 10.129.51.30:7731@17731 myself,master - 0 1646290592000 60 connected 0-5460
27f7e8dede5b68581486ce8cefdd656032baed70 :0@0 master,fail,noaddr - 1646282374602 1646282369596 4 disconnected
91b7f8c79c91c7edd77458c332f0b9299bdb94d4 10.129.51.30:7732@17732 master - 0 1646290592000 63 connected 5461-10922
c3c7ba2d0709121e69c2881724a0c5be903a4a6a 10.129.51.30:7736@17736 slave d1c7d99e13a2d7317baf883dffa906470a606641 
f0e5d3d17babbce85a9290e679a626bc0bbacc93 10.129.51.30:7735@17735 slave 91b7f8c79c91c7edd77458c332f0b9299bdb94d4

日志打印正常，使用都正常。

redis集群在线迁移第二篇（redis迁移后调整主从关系，停掉14机器上的所有从节点）-实战二的更多相关文章

  1. Spring集成Redis集群（含spring集成redis代码）

    代码地址如下:http://www.demodashi.com/demo/11458.html 一.准备工作 安装 Redis 集群 安装参考: http://blog.csdn.net/zk6738 ...

  2. redis集群在线迁移第一篇（数据在线迁移至新集群）实战一

    迁移背景:1.原来redis集群在A机房,需要把其迁移到新机房B上来.2.保证现有环境稳定.3.采用在线迁移方式,因为原有redis集群内有大量数据.4.如果是一个全新的redis集群搭建会简单很多. ...

  3. Redis集群~windows下搭建Sentinel环境及它对主从模式的实际意义

    回到目录 关于redis-sentinel出现的原因 Redis集群的主从模式有个最大的弊端,就是当主master挂了之前,它的slave从服务器无法提升为主,而在redis-sentinel出现之后 ...

  4. redis集群在线迁移

    地址规划 主机名 ip地 端口 redis01 10.0.0.10 6379.6380 redis02 10.0.0.60 6379.6380 redis03 10.0.0.61 6379.6380 ...

  5. Linux 下Redis集群安装部署及使用详解(在线和离线两种安装+相关错误解决方案)

    一.应用场景介绍 本文主要是介绍Redis集群在Linux环境下的安装讲解,其中主要包括在联网的Linux环境和脱机的Linux环境下是如何安装的.因为大多数时候,公司的生产环境是在内网环境下,无外网 ...

  6. 高性能网站架构设计之缓存篇（6）- Redis 集群（中）

    昨天晚上钓鱼回来,大发神经,写了篇概括程序员生活现状的文章,没想到招来众多人的口诛笔伐,大有上升到政治层面的趋势. 我也许不会再发表任何冲击心灵的文章,我希望给大家带来更多的正能量,所以那篇文章已被我 ...

  7. Bash实践：抽样检测数据迁移至Redis集群后的数据一致性

    熟悉了一段时间的Bash编程,因此借此任务操作一把bash编程,主要涉及到Redis单节点与Redis集群的操作 1. 任务背景 近日有个任务需要将历史的Redis(主从节点)中的数据迁移至Redis ...

  8. [个人翻译]Redis 集群教程（上）

    官方原文地址:https://redis.io/topics/cluster-tutorial  水平有限,如果您在阅读过程中发现有翻译的不合理的地方,请留言,我会尽快修改,谢谢.        这是 ...

  9. Redis集群~StackExchange.redis连接Twemproxy代理服务器

    回到目录 本文是Redis集群系列的一篇文章,主要介绍使用StackExchange.Redis进行Twemproxy(文中简称TW)代理服务的连接过程,事务上,对于TW来说,我们需要理解一下它的物理 ...

随机推荐

  1. CF594D题解

    我不会数据结构/kk 我想题意应该十分清楚了. 我们知道 \(\varphi(p^k)=p^{k-1}(p-1)\),那么我们考虑将一个询问下放到右端点,然后往右移动右端点并更新每个左端点到右端点的答 ...

  2. G1垃圾回收器在并发场景调优

    一.序言 目前企业级主流使用的Java版本是8,垃圾回收器支持手动修改为G1,G1垃圾回收器是Java 11的默认设置,因此G1垃圾回收器可以用很长时间,现阶段垃圾回收器优化意味着针对G1垃圾回收器优 ...

  3. C#/VB.NET 将Html转为Excel

    本文介绍通过C#和VB.NET代码展示将Html转为Excel文档的方法. dll引用 方法1 将 Spire.XLS for .NET 下载到本地,解压,安装.完成安装后,在安装路径下找到BIN文件 ...

  4. 安全学习笔记-web安全之XSS攻击

    web安全之XSS攻击 XSS 即跨站脚本攻击,是 OWASP TOP10 之一.它的全称为 Cross-site scripting,因为 CSS 这个简称已经被占用表示为前端三剑客之一的CSS,所 ...

  5. 4月28日 python学习总结 线程与协程

    一. 异步与回调机制 问题: 1.任务的返回值不能得到及时的处理,必须等到所有任务都运行完毕才能统一进行处理 2.解析的过程是串行执行的,如果解析一次需要花费2s,解析9次则需要花费18s 解决一: ...

  6. Windows服务器上搭建Windows2003+IIS+ASP.NET+MSSQL网站

    一.安装IIS服务 1. 选择"开始"→"所有程序"→"管理工具"→"管理您的服务器"菜单命令,启动"添加或删 ...

  7. luoguP6620 [省选联考 2020 A 卷] 组合数问题(斯特林数)

    luoguP6620 [省选联考 2020 A 卷] 组合数问题(斯特林数) Luogu 题外话: LN切这题的人比切T1的多. 我都想到了组合意义乱搞也想到可能用斯特林数为啥还是没做出来... 我怕 ...

  8. 22.2.14session和反反爬处理

    22.2.14 session和反反爬处理 1.session: requests库包含session,都是用来对一个url发送请求,区别在于session是一连串的请求,在session请求过程中c ...

  9. java线程池源码分析

    我们在关闭线程池的时候会使用shutdown()和shutdownNow(),那么问题来了: 这两个方法又什么区别呢? 他们背后的原理是什么呢? 线程池中线程超过了coresize后会怎么操作呢? 为 ...

  10. 什么是 Daemon 线程？它有什么意义？

    所谓后台(daemon)线程,是指在程序运行的时候在后台提供一种通用服务的线 程,并且这个线程并不属于程序中不可或缺的部分.因此,当所有的非后台线程 结束时,程序也就终止了,同时会杀死进程中的所有后台 ...