redis cluster異地數據遷移，擴容，縮容

由於項目的服務器分布在重慶，上海，台北，休斯頓，所以需要做異地容災需求。當前的mysql，redis cluster，elastic search都在重慶的如果重慶停電了，整個應用都不能用了。

現在考慮第一步做重慶和上海的異地容災，大概測試了一下重慶的幾台服務器之間大概是13m/s的傳輸速度也就是說100M的局域網帶寬，重慶到上海只有1.2m/s的傳輸速度，大概10M的局域網帶寬。

第一個方案先考慮簡單的  mysql 重慶上海主主同步  redis cluster的master節點默認都設置在重慶的服務器，slave都設置在上海服務器。es的主分片也設置在重慶，副本分片全部設置在上海。

 

如下是redis的擴容和數據遷移的方法

在trialrun的服務器上一共3台   15.99.72.164和15.99.72.165在重慶    15.15.181.147在上海

 

[root@sha-147 7005]# bin/redis-cli -c -h 15.15.181.147 -p 7006
15.15.181.147:7006> cluster nodes
c08e8c7faeede2220e621b2409061210e0b107ad 15.99.72.164:7001@17001 slave 421123bf7fb3a4061e34cab830530d87b21148ee 0 1577089232000 7 connected
733609c2fbecdd41f454363698514e2f72ee0208 15.15.181.147:7006@17006 myself,slave f452a66121e1e9c02b0ed28cafe03aaddb327c36 0 1577089230000 6 connected
31670db07d1bc7620a8f8254b26f2af00b04d1fd 15.99.72.164:7002@17002 slave 763a88d5328ab0ce07a312e726d78bb2141b5813 0 1577089234988 5 connected
f452a66121e1e9c02b0ed28cafe03aaddb327c36 15.99.72.165:7003@17003 master - 0 1577089235796 3 connected 5461-10922
421123bf7fb3a4061e34cab830530d87b21148ee 15.99.72.165:7004@17004 master - 0 1577089234000 7 connected 0-5460
763a88d5328ab0ce07a312e726d78bb2141b5813 15.15.181.147:7005@17005 master - 0 1577089232733 5 connected 10923-16383

 

 

[root@cq-165 src]# /root/tools/redis-4.0.11/src/redis-trib.rb info 15.99.72.165:7003
15.99.72.165:7003 (f452a661...) -> 53254 keys | 5462 slots | 1 slaves.
15.15.181.147:7005 (763a88d5...) -> 53174 keys | 5461 slots | 1 slaves.
15.99.72.165:7004 (421123bf...) -> 53050 keys | 5461 slots | 1 slaves.
[OK] 159478 keys in 3 masters.
9.73 keys per slot on average.

 

 

之前安裝的是三主三從，現在我需要在165上先安裝一個7007 的master的節點加入之前的集群然后把15.15.181.147:7005@17005 master  的slots 全部遷移到165的7007節點

 

1，先在165上  mkdir -p /usr/local/redis-cluster/7007

由於之前165上安裝過其他節點，直接  cd /usr/local/redis-ii/

cp -r bin /usr/local/redis-cluster/7007

然后進入之前安裝的7004節點 cd /usr/local/redis-cluster/7004

cp redis.conf ../7007/

然后修改7007的相關配置

 

bind 15.99.72.165
protected-mode no
port 7007
daemonize yes
cluster-enabled yes
cluster-node-timeout 15000 

 

保存配置后，啟動7007這個節點  bin/redis-server ./redis.conf

 

然后把165:7007節點添加到之前的節點中

 

[root@cq-165 tools]# /root/tools/redis-4.0.11/src/redis-trib.rb add-node 15.99.72.165:7007 15.99.72.165:7003
>>> Adding node 15.99.72.165:7007 to cluster 15.99.72.165:7003
>>> Performing Cluster Check (using node 15.99.72.165:7003)
M: f452a66121e1e9c02b0ed28cafe03aaddb327c36 15.99.72.165:7003
slots:5461-10922 (5462 slots) master
1 additional replica(s)
M: 763a88d5328ab0ce07a312e726d78bb2141b5813 15.15.181.147:7005
slots:10923-16383 (5461 slots) master
1 additional replica(s)
M: 421123bf7fb3a4061e34cab830530d87b21148ee 15.99.72.165:7004
slots:0-5460 (5461 slots) master
1 additional replica(s)
S: 733609c2fbecdd41f454363698514e2f72ee0208 15.15.181.147:7006
slots: (0 slots) slave
replicates f452a66121e1e9c02b0ed28cafe03aaddb327c36
S: 31670db07d1bc7620a8f8254b26f2af00b04d1fd 15.99.72.164:7002
slots: (0 slots) slave
replicates 763a88d5328ab0ce07a312e726d78bb2141b5813
S: c08e8c7faeede2220e621b2409061210e0b107ad 15.99.72.164:7001
slots: (0 slots) slave
replicates 421123bf7fb3a4061e34cab830530d87b21148ee
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 15.99.72.165:7007 to make it join the cluster.
[OK] New node added correctly.

 

 

再用cluster nodes命令查看當前節點，可以發現7007已經加入到了redis cluster中但是slot 數為0

 

15.15.181.147:7006> cluster nodes
8e134e67e4e83a613b90f67cc6e6b8d71c208886 15.99.72.165:7007@17007 master - 0 1577095695760 0 connected
c08e8c7faeede2220e621b2409061210e0b107ad 15.99.72.164:7001@17001 slave 421123bf7fb3a4061e34cab830530d87b21148ee 0 1577095693561 7 connected
733609c2fbecdd41f454363698514e2f72ee0208 15.15.181.147:7006@17006 myself,slave f452a66121e1e9c02b0ed28cafe03aaddb327c36 0 1577095691000 6 connected
31670db07d1bc7620a8f8254b26f2af00b04d1fd 15.99.72.164:7002@17002 slave 763a88d5328ab0ce07a312e726d78bb2141b5813 0 1577095695000 5 connected
f452a66121e1e9c02b0ed28cafe03aaddb327c36 15.99.72.165:7003@17003 master - 0 1577095694000 3 connected 5461-10922
421123bf7fb3a4061e34cab830530d87b21148ee 15.99.72.165:7004@17004 master - 0 1577095694763 7 connected 0-5460
763a88d5328ab0ce07a312e726d78bb2141b5813 15.15.181.147:7005@17005 master - 0 1577095691699 5 connected 10923-16383

 

接下來需要把15.15.181.147:7005@17005 master  的slots全部遷移到 15.99.72.165:7007@17007 master 上

 

 

遷移過程參考如下例子，由於我遷移的時候打印太多，沒有拷貝粘貼進來，和下面除了ip 和port等等有區別級別上一樣

重新分配master節點分配slot

將192.168.1.116:7000的slot全部分配（5461）給192.168.1.117:7000

[root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb reshard 192.168.1.117:7000
How many slots do you want to move (from 1 to 16384)? 5461      # 分配多少數量的slot
What is the receiving node ID? a6d7dacd679a96fd79b7de552428a63610d620e6   # 上面那些數量的slot被哪個節點接收。這里填寫192.168.1.117:7000節點ID
  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:0607089e5bb3192563bd8082ff230b0eb27fbfeb #指從哪個節點分配上面指定數量的slot。這里填寫192.168.1.116:7000的ID。如果填寫all，則表示從之前所有master節點中抽取上面指定數量的slot。
Source node #2:done
Do you want to proceed with the proposed reshard plan (yes/no)? yes
Moving slot 0 from 192.168.1.116:7000 to 192.168.1.117:7000: 
[ERR] Calling MIGRATE: ERR Syntax error, try CLIENT (LIST | KILL | GETNAME | SETNAME | PAUSE | REPLY)

解決報錯

[root@localhost redis-cluster]# cp redis-4.0.6/src/redis-trib.rb redis-4.0.6/src/redis-trib.rb.bak 將redis-trib.rb文件中原來的 source.r.client.call(["migrate",target.info[:host],target.info[:port],"",0,@timeout,:keys,*keys]) source.r.client.call(["migrate",target.info[:host],target.info[:port],"",0,@timeout,:replace,:keys,*keys]) 改為 source.r.call(["migrate",target.info[:host],target.info[:port],"",0,@timeout,"replace",:keys,*keys]) source.r.call(["migrate",target.info[:host],target.info[:port],"",0,@timeout,:replace,:keys,*keys]) [root@localhost redis-cluster]# cat redis-4.0.6/src/redis-trib.rb |grep source.r.call source.r.call(["migrate",target.info[:host],target.info[:port],"",0,@timeout,"replace",:keys,*keys]) source.r.call(["migrate",target.info[:host],target.info[:port],"",0,@timeout,:replace,:keys,*keys]) # 修改后繼續報錯 [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb reshard 192.168.1.117:7000 [OK] All nodes agree about slots configuration. >>> Check for open slots... [WARNING] Node 192.168.1.117:7000 has slots in importing state (0). [WARNING] Node 192.168.1.116:7000 has slots in migrating state (0). [WARNING] The following slots are open: 0 >>> Check slots coverage... [OK] All 16384 slots covered. *** Please fix your cluster problems before resharding # 解決辦法 [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-cli -h 192.168.1.117 -c -p 7000 192.168.1.117:7000> cluster setslot 0 stable #The following slots are open: 0 這里是多少就寫多少 OK 192.168.1.117:7000> exit [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-cli -h 192.168.1.116 -c -p 7000 192.168.1.116:7000> cluster setslot 0 stable #The following slots are open: 0 這里是多少就寫多少 OK 192.168.1.116:7000> exit [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb fix 192.168.1.117:7000 [OK] All nodes agree about slots configuration. >>> Check for open slots... >>> Check slots coverage... [OK] All 16384 slots covered. 

在重新分槽

[root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb reshard 192.168.1.117:7000
How many slots do you want to move (from 1 to 16384)? 5461      # 分配多少數量的slot
What is the receiving node ID? a6d7dacd679a96fd79b7de552428a63610d620e6   # 上面那些數量的slot被哪個節點接收。這里填寫192.168.1.117:7000節點ID
  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:0607089e5bb3192563bd8082ff230b0eb27fbfeb #指從哪個節點分配上面指定數量的slot。這里填寫192.168.1.116:7000的ID。如果填寫all，則表示從之前所有master節點中抽取上面指定數量的slot。
Source node #2:done
Do you want to proceed with the proposed reshard plan (yes/no)? yes
Moving slot 5457 from 192.168.1.116:7000 to 192.168.1.117:7000: ..
Moving slot 5458 from 192.168.1.116:7000 to 192.168.1.117:7000: .
Moving slot 5459 from 192.168.1.116:7000 to 192.168.1.117:7000: 
Moving slot 5460 from 192.168.1.116:7000 to 192.168.1.117:7000: ..

檢查分槽結果

# 可以看到 192.168.1.116:7000 上的slot已經移動到 192.168.1.117:7000節點了 [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb info 192.168.1.117:7000 192.168.1.117:7000 (a6d7dacd...) -> 6652 keys | 5461 slots | 2 slaves. 192.168.1.117:7004 (63893e74...) -> 0 keys | 0 slots | 1 slaves. 192.168.1.117:7002 (8540a78c...) -> 0 keys | 0 slots | 1 slaves. 192.168.1.116:7001 (17831f8b...) -> 6665 keys | 5461 slots | 1 slaves. 192.168.1.116:7003 (c433ff1b...) -> 6683 keys | 5462 slots | 1 slaves. 192.168.1.116:7000 (0607089e...) -> 0 keys | 0 slots | 0 slaves. 

將192.168.1.116:7001的slot全部分配（5461）給192.168.1.117:7002

[root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb reshard 192.168.1.117:7002 How many slots do you want to move (from 1 to 16384)? 5461 What is the receiving node ID? 8540a78c666cb1e81fb2821d112f3040542af056 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:17831f8bbcd43ac05efc5486ebfcdbb210ce48f0 Source node #2:done ...... Moving slot 16381 from 17831f8bbcd43ac05efc5486ebfcdbb210ce48f0 Moving slot 16382 from 17831f8bbcd43ac05efc5486ebfcdbb210ce48f0 Moving slot 16383 from 17831f8bbcd43ac05efc5486ebfcdbb210ce48f0 Do you want to proceed with the proposed reshard plan (yes/no)? yes ...... Moving slot 16381 from 192.168.1.116:7001 to 192.168.1.117:7002: Moving slot 16382 from 192.168.1.116:7001 to 192.168.1.117:7002: . Moving slot 16383 from 192.168.1.116:7001 to 192.168.1.117:7002: .. 

將192.168.1.116:7003的slot全部分配（5462）給192.168.1.117:7004

[root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb reshard 192.168.1.117:7004 How many slots do you want to move (from 1 to 16384)? 5462 What is the receiving node ID? 63893e74e6f8e2414eba97b094a80ae8b3caeb09 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:c433ff1b448fbcd3234632712643bc68d5213e3b Source node #2:done ...... Moving slot 10920 from c433ff1b448fbcd3234632712643bc68d5213e3b Moving slot 10921 from c433ff1b448fbcd3234632712643bc68d5213e3b Moving slot 10922 from c433ff1b448fbcd3234632712643bc68d5213e3b Do you want to proceed with the proposed reshard plan (yes/no)? yes ...... Moving slot 10920 from 192.168.1.116:7003 to 192.168.1.117:7004: .. Moving slot 10921 from 192.168.1.116:7003 to 192.168.1.117:7004: .. Moving slot 10922 from 192.168.1.116:7003 to 192.168.1.117:7004: 

查看最新分槽情況

[root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb info 192.168.1.117:7000 192.168.1.117:7004 (63893e74...) -> 6683 keys | 5462 slots | 2 slaves. 192.168.1.116:7003 (c433ff1b...) -> 0 keys | 0 slots | 0 slaves. 192.168.1.117:7002 (8540a78c...) -> 6665 keys | 5461 slots | 2 slaves. 192.168.1.116:7000 (0607089e...) -> 0 keys | 0 slots | 0 slaves. 192.168.1.117:7000 (a6d7dacd...) -> 6652 keys | 5461 slots | 2 slaves. 192.168.1.116:7001 (17831f8b...) -> 0 keys | 0 slots | 0 slaves. [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb check 192.168.1.117:7000 >>> Performing Cluster Check (using node 192.168.1.117:7000) M: a6d7dacd679a96fd79b7de552428a63610d620e6 192.168.1.117:7000 slots:0-5460 (5461 slots) master 2 additional replica(s) M: 63893e74e6f8e2414eba97b094a80ae8b3caeb09 192.168.1.117:7004 slots:5461-10922 (5462 slots) master 2 additional replica(s) M: 8540a78c666cb1e81fb2821d112f3040542af056 192.168.1.117:7002 slots:10923-16383 (5461 slots) master 2 additional replica(s) S: 1ebeedb98619bc88bf36acbbe4a766f2f74e629f 192.168.1.117:7003 slots: (0 slots) slave replicates 8540a78c666cb1e81fb2821d112f3040542af056 M: 17831f8bbcd43ac05efc5486ebfcdbb210ce48f0 192.168.1.116:7001 slots: (0 slots) master 0 additional replica(s) S: e010d410223a2376d3308a68a724bac27ef8d74f 192.168.1.117:7001 slots: (0 slots) slave replicates a6d7dacd679a96fd79b7de552428a63610d620e6 S: 17ee6bd4c68235d09acf2f4b18ae3fcc649d629c 192.168.1.116:7002 slots: (0 slots) slave replicates 63893e74e6f8e2414eba97b094a80ae8b3caeb09 M: c433ff1b448fbcd3234632712643bc68d5213e3b 192.168.1.116:7003 slots: (0 slots) master 0 additional replica(s) S: bef4dddc01651d64b5bb3e0ac384c0eb120aa537 192.168.1.116:7004 slots: (0 slots) slave replicates a6d7dacd679a96fd79b7de552428a63610d620e6 S: 2579ab004e277ba68197d851d47d0436e0cf203d 192.168.1.117:7005 slots: (0 slots) slave replicates 63893e74e6f8e2414eba97b094a80ae8b3caeb09 S: fb8dc97c90f3edc7f10a385f4b4b2a2b2612ffab 192.168.1.116:7005 slots: (0 slots) slave replicates 8540a78c666cb1e81fb2821d112f3040542af056 M: 0607089e5bb3192563bd8082ff230b0eb27fbfeb 192.168.1.116:7000 slots: (0 slots) master 0 additional replica(s) [OK] All nodes agree about slots configuration. >>> Check for open slots... >>> Check slots coverage... [OK] All 16384 slots covered. 

 

驗證遷移后數據

[root@localhost redis-cluster]# ./redis-4.0.6/src/redis-cli -h 192.168.1.117 -p 7000 -c dbsize (integer) 6652 [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-cli -h 192.168.1.117 -p 7002 -c dbsize (integer) 6665 [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-cli -h 192.168.1.117 -p 7004 -c dbsize (integer) 6683 [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-cli -h 192.168.1.117 -p 7000 -c 192.168.1.117:7000> keys * ...... 6650) "name7710" 6651) "name16668" 6652) "name12290" 192.168.1.117:7000> 

遷移后從集群中刪除原來的節點

查看舊集群節點地址及node id

[root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb check 192.168.1.117:7000 | grep 192.168.1.116 M: 17831f8bbcd43ac05efc5486ebfcdbb210ce48f0 192.168.1.116:7001 S: 17ee6bd4c68235d09acf2f4b18ae3fcc649d629c 192.168.1.116:7002 M: c433ff1b448fbcd3234632712643bc68d5213e3b 192.168.1.116:7003 S: bef4dddc01651d64b5bb3e0ac384c0eb120aa537 192.168.1.116:7004 S: fb8dc97c90f3edc7f10a385f4b4b2a2b2612ffab 192.168.1.116:7005 M: 0607089e5bb3192563bd8082ff230b0eb27fbfeb 192.168.1.116:7000 

刪除舊集群中的slave節點

[root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb del-node 192.168.1.116:7002 17ee6bd4c68235d09acf2f4b18ae3fcc649d629c >>> Removing node 17ee6bd4c68235d09acf2f4b18ae3fcc649d629c from cluster 192.168.1.116:7002 >>> Sending CLUSTER FORGET messages to the cluster... >>> SHUTDOWN the node. [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb del-node 192.168.1.116:7004 bef4dddc01651d64b5bb3e0ac384c0eb120aa537 >>> Removing node bef4dddc01651d64b5bb3e0ac384c0eb120aa537 from cluster 192.168.1.116:7004 >>> Sending CLUSTER FORGET messages to the cluster... >>> SHUTDOWN the node. [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb del-node 192.168.1.116:7005 fb8dc97c90f3edc7f10a385f4b4b2a2b2612ffab >>> Removing node fb8dc97c90f3edc7f10a385f4b4b2a2b2612ffab from cluster 192.168.1.116:7005 >>> Sending CLUSTER FORGET messages to the cluster... >>> SHUTDOWN the node. 

查看刪除后的節點信息

[root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb check 192.168.1.117:7000 | grep 192.168.1.116 M: 17831f8bbcd43ac05efc5486ebfcdbb210ce48f0 192.168.1.116:7001 M: c433ff1b448fbcd3234632712643bc68d5213e3b 192.168.1.116:7003 M: 0607089e5bb3192563bd8082ff230b0eb27fbfeb 192.168.1.116:7000 

刪除舊集群中的master節點

刪除master注意細節：
  如果還有slave節點，需要先將slave轉移到其他master節點或刪除slave節點
  如果master節點有slot，去掉分配的slot，然后再刪除master節點。
  刪除master主節點時，必須確保它上面的slot為0. 否則可能會導致整個redis cluster集群無法工作！ 如果要移除的master節點不是空的，需要先用重新分片命令來把數據移到其他的節點。 [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb del-node 192.168.1.116:7000 0607089e5bb3192563bd8082ff230b0eb27fbfeb >>> Removing node 0607089e5bb3192563bd8082ff230b0eb27fbfeb from cluster 192.168.1.116:7000 >>> Sending CLUSTER FORGET messages to the cluster... >>> SHUTDOWN the node. [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb del-node 192.168.1.116:7001 17831f8bbcd43ac05efc5486ebfcdbb210ce48f0 >>> Removing node 17831f8bbcd43ac05efc5486ebfcdbb210ce48f0 from cluster 192.168.1.116:7001 >>> Sending CLUSTER FORGET messages to the cluster... >>> SHUTDOWN the node. [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb del-node 192.168.1.116:7003 c433ff1b448fbcd3234632712643bc68d5213e3b >>> Removing node c433ff1b448fbcd3234632712643bc68d5213e3b from cluster 192.168.1.116:7003 >>> Sending CLUSTER FORGET messages to the cluster... >>> SHUTDOWN the node. 

查看現有的節點信息

[root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb check 192.168.1.117:7000 >>> Performing Cluster Check (using node 192.168.1.117:7000) M: a6d7dacd679a96fd79b7de552428a63610d620e6 192.168.1.117:7000 slots:0-5460 (5461 slots) master 1 additional replica(s) M: 63893e74e6f8e2414eba97b094a80ae8b3caeb09 192.168.1.117:7004 slots:5461-10922 (5462 slots) master 1 additional replica(s) M: 8540a78c666cb1e81fb2821d112f3040542af056 192.168.1.117:7002 slots:10923-16383 (5461 slots) master 1 additional replica(s) S: 1ebeedb98619bc88bf36acbbe4a766f2f74e629f 192.168.1.117:7003 slots: (0 slots) slave replicates 8540a78c666cb1e81fb2821d112f3040542af056 S: e010d410223a2376d3308a68a724bac27ef8d74f 192.168.1.117:7001 slots: (0 slots) slave replicates a6d7dacd679a96fd79b7de552428a63610d620e6 S: 2579ab004e277ba68197d851d47d0436e0cf203d 192.168.1.117:7005 slots: (0 slots) slave replicates 63893e74e6f8e2414eba97b094a80ae8b3caeb09 [OK] All nodes agree about slots configuration. >>> Check for open slots... >>> Check slots coverage... [OK] All 16384 slots covered. [root@localhost redis-cluster]# ./redis-4.0.6/src/redis-trib.rb info 192.168.1.117:7000 192.168.1.117:7000 (a6d7dacd...) -> 6652 keys | 5461 slots | 1 slaves. 192.168.1.117:7004 (63893e74...) -> 6683 keys | 5462 slots | 1 slaves. 192.168.1.117:7002 (8540a78c...) -> 6665 keys | 5461 slots | 1 slaves. [OK] 20000 keys in 3 masters.

 

 

 

2，添加主節點

# redis-trib.rb add-node 192.168.10.219:6378 192.168.10.219:6379

注釋：

192.168.10.219:6378是新增的節點

192.168.10.219:6379集群任一個舊節點

3，添加從節點

# redis-trib.rb add-node --slave --master-id 03ccad2ba5dd1e062464bc7590400441fafb63f2 192.168.10.220:6385 192.168.10.219:6379

注釋：

--slave，表示添加的是從節點

--master-id 03ccad2ba5dd1e062464bc7590400441fafb63f2,主節點的node id，在這里是前面新添加的6378的node id

192.168.10.220:6385,新節點

192.168.10.219:6379集群任一個舊節點

 

 

 

 

 

 

 

參考：

https://www.jianshu.com/p/925f69f2fc35
https://www.cnblogs.com/kevingrace/p/9844310.html