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.cnblogs.com/kevingrace/p/9844310.html
redis cluster异地数据迁移，扩容，缩容的更多相关文章
- Redis Cluster 自动化安装，扩容和缩容
Redis Cluster 自动化安装,扩容和缩容 之前写过一篇基于python的redis集群自动化安装的实现,基于纯命令的集群实现还是相当繁琐的,因此官方提供了redis-trib.rb这个工具虽 ...
- redis 3.0 集群__数据迁移和伸缩容
添加节点 1,启动2个新的redis-sever, 参照 ( redis 3.0 集群____安装 ),端口号为 7007 和 7008 2,使用命令 redis-trib.rb add-node 命 ...
- Redis Cluster 的数据分片机制
上一篇<分布式数据缓存中的一致性哈希算法> 文章中讲述了一致性哈希算法的基本原理和实现,今天就以 Redis Cluster 为例,详细讲解一下分布式数据缓存中的数据分片,上线下线时数据迁 ...
- codis__数据迁移和伸缩容
数据迁移命令 注意点:是迁移到某个 redis-group 而不是某个redis-servers 实例 伸缩容用法 redis 内存等不够用时 增容 : 增加redis-group, 然后迁移使用上 ...
- Redis单实例数据迁移到集群
环境说明 单机redis redis集群 192.168.41.101:7000 master 192.168.41.101:7001 master 192.168.41.102:7000 maste ...
- LVM划分磁盘及扩容缩容
lvm:logical volume monitor 逻辑卷管理器 作用: 采用lvm划分磁盘:磁盘空间不够时,方便扩展磁盘.物理卷加到卷组时被划分等大的pe,即pv是由众多pe构成.pe是卷组的最小 ...
- redis集群数据迁移
redis集群数据备份迁移方案 n 迁移环境描述及分析 当前我们面临的数据迁移环境是:集群->集群. 源集群: 源集群为6节点,3主3备 主 备 192.168.112.33:8001 192 ...
- redis集群数据迁移txt版
./redis-trib.rb create --replicas 1 192.168.112.33:8001 192.168.112.33:8002 192.168.112.33:8003 192. ...
- LVM常规操作记录梳理（扩容/缩容/快照等）
基本介绍Linux用户安装Linux 操作系统时遇到的一个最常见的难以决定的问题就是如何正确地给评估各分区大小,以分配合适的硬盘空间.随着 Linux的逻辑盘卷管理功能的出现,这些问题都迎刃而解, l ...
随机推荐
- String,StringBuilder 和StringBuffer区别
1. String 和字符串缓冲区的区别是: String 是一个不可变的字符序列 , 而字符串缓冲区是可变的 2. StringBuffer 是一个线程安全的可变字符序列 ; 线程安全对应的效率低 ...
- ISO/IEC 9899:2011 条款6.4.2——标识符
6.4.2 标识符 6.4.2.1 通用 语法 1.identifier: identifier-nodigit identifier identifier-nondigit identifie ...
- springboot集成调用Azkaban
springboot集成调用Azkaban 一. 说明 1.Azkaban是由Linkedin公司推出的一个批量工作流任务调度器,主要用于在一个工作流内以一个特定的顺序运行一组工作和流程,它的配置是通 ...
- Laravel 项目开发环境配置
1.首先安装Laravel 依赖管理包工具 Composer (前提是本地装好了PHP php -v) php -r "copy('https://install.phpcomposer. ...
- Pyhthon3之使用__slots__
正常情况下,我们定义了一个class,创建了一个class实例后,我们可以给该实例绑定任何属性和方法,这就是动态语言的灵活性.先定义class: >>> class Student( ...
- ELK之elasticsearch7版本集群设置
ELK7版本搭建参考:https://www.cnblogs.com/minseo/p/10948632.html node-1已经安装配置好 配置文件如下 [root@salt-test conf. ...
- 阿里云ECS服务器活动99元一年（2019年 Hi拼团，拼着买，更划算）
2019年10月22日更新,阿里云推荐有礼活动:ECS突发性能T6-低至99元/年赶紧上车~ 低价高性能,拼着买更划算 点我参加活动>> 购买前领取阿里云幸运券,更有可能享受折上折的优惠. ...
- 【计算机视觉】Selective Search for Object Recognition论文阅读1
Selective Search for Object Recognition 作者: J. R. R. Uijlings, K. E. A. van de Sande, T. Gevers, A. ...
- CMake生成VS2010工程相对路径和绝对路径问题说明
CMake生成VS2010工程相对路径和绝对路径问题说明 声明:引用请注明出处http://blog.csdn.net/lg1259156776/ 主要是使用CMake生成的VS2010的工程,最好不 ...
- PHP解析xml的方法
PHP解析xml的方法<pre><?php /** XML 文件分析类 * Date: 2013-02-01 * Author: fdipzone * Ver: 1.0 * * fu ...