root@redis-server1:~# redis-cli -h 192.168.100.161192.168.100.161:6379> auth q1w2e3r4ys@123OK192.168.100.161:6379> set aaa 111OK
----查看slave1 数据----root@redis-server2:~# redis-cli -h 192.168.100.162192.168.100.163:6379> auth q1w2e3r4ys@123192.168.100.162:6379> set aaa xxx(error) READONLY You can't write against a read only replica.192.168.100.162:6379> get aaa"111"----查看slave2 数据----root@redis-server3:~# redis-cli -h 192.168.100.163192.168.100.163:6379> auth q1w2e3r4ys@123OK192.168.100.163:6379> set aaa xxx(error) READONLY You can't write against a read only replica.192.168.100.163:6379> get aaa"111"
root@ubuntu20:~# tail -f /apps/redis/logs/redis_6379.log190032:C 11 Sep 2023 08:08:00.093 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB187211:M 11 Sep 2023 08:08:00.093 * Diskless rdb transfer, done reading from pipe, 1 replicas still up.187211:M 11 Sep 2023 08:08:00.098 * Background RDB transfer terminated with success187211:M 11 Sep 2023 08:08:00.099 * Streamed RDB transfer with replica 192.168.100.162:6379 succeeded (socket). Waiting for REPLCONF ACK from replica to enable streaming187211:M 11 Sep 2023 08:08:00.099 * Synchronization with replica 192.168.100.162:6379 succeeded187211:M 11 Sep 2023 08:40:18.022 * 1 changes in 3600 seconds. Saving...187211:M 11 Sep 2023 08:40:18.024 * Background saving started by pid 190870190870:C 11 Sep 2023 08:40:18.069 * DB saved on disk190870:C 11 Sep 2023 08:40:18.072 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB187211:M 11 Sep 2023 08:40:18.125 * Background saving terminated with success
root@redis-s2:~# redis-cli -h 192.168.100.162 -a q1w2e3r4ys@123192.168.100.162:6379> SLAVEOF no oneOK
root@redis-s2:~# redis-cli -h 192.168.100.162 -a q1w2e3r4ys@123192.168.100.162:6379> SLAVEOF 192.168.100.161 6379OK192.168.100.162:6379> CONFIG SET masterauth q1w2e3r4ys@123OK
root@redis-s2:~# tail -f -n 200 /apps/redis/logs/redis_6379.log70122:S 04 Sep 2023 12:41:12.094 # MASTER aborted replication with an error: NOAUTH Authentication required.70122:S 04 Sep 2023 12:41:12.095 * Reconnecting to MASTER 172.31.7.201:6379 after failure70122:S 04 Sep 2023 12:41:12.095 * MASTER <-> REPLICA sync started70122:S 04 Sep 2023 12:41:12.095 * Non blocking connect for SYNC fired the event.70122:S 04 Sep 2023 12:41:12.096 * Master replied to PING, replication
192.168.100.161:6379> info Replication# Replicationrole:masterconnected_slaves:1slave0:ip=192.168.100.162,port=6379,state=online,offset=4579365,lag=1master_failover_state:no-failovermaster_replid:4a334697d807a6ff1e19b936ae60a399de4bbecb #指向⾃⼰master_replid2:00000000000000000000000000000000000000001.1.1.4：主从复制过程：Redis主从同步可以让从服务器从主服务器备份数据，主从复制分为全量同步和增量同步，⾸次同步是全量同步，⽽且从服务器还可与有从服务器，redis的主从同步是⾮阻塞的master_repl_offset:4579365second_repl_offset:-1repl_backlog_active:1repl_backlog_size:536870912repl_backlog_first_byte_offset:2repl_backlog_histlen:4579364
----slave设置了只读后不能写⼊数据，否则报错如下：----192.168.100.162:6379> SET key111 value111(error) READONLY You can't write against a read only replica.
root@redis-s2:~# redis-cli -h 192.168.100.162 -a q1w2e3r4ys@123192.168.100.162:6379> SLAVEOF no oneOK
----master写入数据----root@redis-server1:~# redis-cli -h 192.168.100.161 -a q1w2e3r4ys@123192.168.100.161:6379> set aaa 111OK192.168.100.161:6379> get aaa"111"----slave验证状态及数据----root@redis-server2:~# redis-cli -h 192.168.100.162 -a q1w2e3r4ys@123192.168.100.162:6379> get aaa"111"192.168.100.162:6379> info Replication# Replicationrole:slavemaster_host:192.168.100.161master_port:6379master_link_status:upmaster_last_io_seconds_ago:1....root@redis-server3:/data/sentinel# redis-cli -h 192.168.100.163 -a q1w2e3r4ys@123192.168.100.163:6379> get aaa"111"192.168.100.163:6379> info Replication# Replicationrole:slavemaster_host:192.168.100.161master_port:6379master_link_status:upmaster_last_io_seconds_ago:1....
----slave 192.168.100.162已经提升为master⻆⾊----192.168.100.162:6379> info Replication# Replicationrole:master #角色为masterconnected_slaves:1slave0:ip=192.168.100.163,port=6379,state=online,offset=568715,lag=0master_failover_state:no-failovermaster_replid:d3e9a41f0954ead87470db8afca23f7c5bb96157master_replid2:3636a0eccdfed789c31a09f72c8c6ea1112c5f19master_repl_offset:568715second_repl_offset:554240repl_backlog_active:1repl_backlog_size:536870912repl_backlog_first_byte_offset:15repl_backlog_histlen:568701
----master被指向了192.168.100.162----192.168.100.163:6379> info Replication# Replicationrole:slavemaster_host:192.168.100.162 #指向slave1为mastermaster_port:6379master_link_status:upmaster_last_io_seconds_ago:0master_sync_in_progress:0slave_read_repl_offset:578921slave_repl_offset:578921slave_priority:100slave_read_only:1replica_announced:1connected_slaves:0master_failover_state:no-failovermaster_replid:d3e9a41f0954ead87470db8afca23f7c5bb96157master_replid2:3636a0eccdfed789c31a09f72c8c6ea1112c5f19master_repl_offset:578921second_repl_offset:554240repl_backlog_active:1repl_backlog_size:536870912repl_backlog_first_byte_offset:91825repl_backlog_histlen:487097
root@redis-server1:~# vi /apps/redis/etc/redis.conf....replicaof 192.168.100.161 6379masterauth q1w2e3r4ys@123# replicaof <masterip> <masterport>....root@redis-server1:~# systemctl restart redis.service----查看当前状态----root@redis-server1:~# redis-cli -h 192.168.100.161 -a q1w2e3r4ys@123192.168.100.161:6379> info Replication# Replicationrole:slavemaster_host:192.168.100.162 #master已经指向redis-server2master_port:6379master_link_status:upmaster_last_io_seconds_ago:1....
root@redis-server2:~# redis-cli -h 192.168.100.162 -a q1w2e3r4ys@123192.168.100.162:6379> info Replication# Replicationrole:masterconnected_slaves:2slave0:ip=192.168.100.163,port=6379,state=online,offset=2705417,lag=0slave1:ip=192.168.100.161,port=6379,state=online,offset=2705417,lag=0master_failover_state:no-failover....
root@redis-server1:~# redis-cli --cluster helpCluster Manager Commands: create host1:port1 ... hostN:portN #创建集群并执⾏节点数 --cluster-replicas <arg> #指定master的副本数量 check <host:port> or <host> <port> - separated by either colon or space #节点地址及IP格式 --cluster-search-multiple-owners #检查是否有槽位同时被分配给了多个节点 info <host:port> or <host> <port> - separated by either colon or space #查看集群主机信息 fix <host:port> or <host> <port> - separated by either colon or space #修复集群 --cluster-search-multiple-owners #修复槽位被同时分配过多个节点的问题 --cluster-fix-with-unreachable-masters #修复不可达的主机 reshard <host:port> or <host> <port> - separated by either colon or space #⼿动热迁移集群指定主机的slots数据到新的⽬的主机(⽤于特定主机维护、下线、更换主机) --cluster-from <arg> --cluster-to <arg> --cluster-slots <arg> --cluster-yes --cluster-timeout <arg> --cluster-pipeline <arg> --cluster-replace rebalance <host:port> or <host> <port> - separated by either colon or space #如果各master的slot槽位差异很⼤(No rebalancing needed! All nodes are within the 2.00%threshold)，可以使⽤rebalance实现⾃动平衡集群中各主机的slot数量 --cluster-weight <node1=w1...nodeN=wN> --cluster-use-empty-masters --cluster-timeout <arg> --cluster-simulate --cluster-pipeline <arg> --cluster-threshold <arg> --cluster-replace add-node new_host:new_port existing_host:existing_port #添加节点到集群 --cluster-slave --cluster-master-id <arg> del-node host:port node_id #从集群删除主机 call host:port command arg arg .. arg #在集群上的所有节点上执⾏命令 --cluster-only-masters --cluster-only-replicas set-timeout host:port milliseconds #设置节点的超时时间 import host:port #将外部redis服务器的数据导⼊到当前集群 --cluster-from <arg> --cluster-from-user <arg> --cluster-from-pass <arg> --cluster-from-askpass --cluster-copy --cluster-replace backup host:port backup_directory #备份集群数据 helpFor check, fix, reshard, del-node, set-timeout, info, rebalance, call, import, backup you can specify the host and port of any working node in the cluster.#check, fix, reshard, del-node, set-timeout, info, rebalance, call, import, backup，可在 任意⼀台节点执⾏Cluster Manager Options: --cluster-yes Automatic yes to cluster commands prompts #交互式的时候⾃动应答 yes
root@redis-server1:~# redis-cli127.0.0.1:6379> auth q1w2e3r4ys@123OK127.0.0.1:6379> info cluster# Clustercluster_enabled:1
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.>>> Performing hash slots allocation on 6 nodes...Master[0] -> Slots 0 - 5460 #⾃动为master分配槽位Master[1] -> Slots 5461 - 10922Master[2] -> Slots 10923 - 16383Adding replica 192.168.100.165:6379 to 192.168.100.161:6379 #自动将192.168.100.165:6379添加为192.168.100.161:6379的slaveAdding replica 192.168.100.166:6379 to 192.168.100.162:6379 #自动将192.168.100.166:6379添加为192.168.100.162：6379的slave
----可以看到slave并没有连接上来----root@redis-server1:~# redis-cli -h 192.168.100.161 -a q1w2e3r4ys@123192.168.100.161:6379> INFO Replication# Replicationrole:masterconnected_slaves:0 #连接的slavemaster_failover_state:no-failovermaster_replid:dc6867acc3e6b76c6c405432eeef60dc56d78493master_replid2:0000000000000000000000000000000000000000master_repl_offset:0second_repl_offset:-1repl_backlog_active:0repl_backlog_size:536870912repl_backlog_first_byte_offset:0repl_backlog_histlen:0
----slave节点修改配置文件----root@redis-server4:~# vi /apps/redis/etc/redis.conmasterauth q1w2e3r4ys@123root@redis-server5:~# vi /apps/redis/etc/redis.conmasterauth q1w2e3r4ys@123root@redis-server6:~# vi /apps/redis/etc/redis.conmasterauth q1w2e3r4ys@123----master节点为了避免重启导致主从重新分配，用命令行修改，同时修改配置文件----root@redis-server1:~# redis-cli -a q1w2e3r4ys@123127.0.0.1:6379> CONFIG SET masterauth q1w2e3r4ys@123OKroot@redis-server2:~# redis-cli -a q1w2e3r4ys@123127.0.0.1:6379> CONFIG SET masterauth q1w2e3r4ys@123OKroot@redis-server3:~# redis-cli -a q1w2e3r4ys@123127.0.0.1:6379> CONFIG SET masterauth q1w2e3r4ys@123OK
----slave已连接----root@redis-server1:~# redis-cli -h 192.168.100.161192.168.100.161:6379> auth q1w2e3r4ys@123OK192.168.100.161:6379> INFO Replication# Replicationrole:masterconnected_slaves:1slave0:ip=192.168.100.165,port=6379,state=online,offset=700,lag=0master_failover_state:no-failovermaster_replid:8f3424563a608c0bc114a661c9333f2ecea0e260master_replid2:0000000000000000000000000000000000000000master_repl_offset:700second_repl_offset:-1repl_backlog_active:1repl_backlog_size:536870912repl_backlog_first_byte_offset:1repl_backlog_histlen:700
root@redis-server4:~# redis-cli -h 192.168.100.164192.168.100.164:6379> auth q1w2e3r4ys@123OK192.168.100.164:6379> info Replication# Replicationrole:slavemaster_host:192.168.100.163master_port:6379master_link_status:upmaster_last_io_seconds_ago:2....
root@redis-server1:~# redis-cli -h 192.168.100.161 -a q1w2e3r4ys@123192.168.100.161:6379> set qbn aaaOK192.168.100.161:6379> set qbn2 bbb #经过算法计算，当前key不在master1槽位，无法写入(error) MOVED 16382 192.168.100.163:6379 #提示槽位在master3----master3成功写入----root@redis-server3:~# redis-cli -h 192.168.100.163 -a q1w2e3r4ys@123192.168.100.163:6379> set qbn2 bbbOK192.168.100.163:6379> get qbn2"bbb"
----安装python3以及redis-py-cluster模块----root@redis-server8:~# apt install python3-piproot@redis-server8:~# pip3 --versionpip 20.0.2 from /usr/lib/python3/dist-packages/pip (python 3.8)root@redis-server8:~# mkdir ~/.piproot@redis-server8:~# vim ~/.pip/pip.conf[global]index-url = https://mirrors.aliyun.com/pypi/simple/[install]trusted-host=mirrors.aliyun.comroot@redis-server8:~# pip3 install redis-py-cluster
----对应槽位的key在master可读写----root@redis-server1:~# redis-cli -h 192.168.100.164 -a q1w2e3r4ys@123Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.192.168.100.164:6379> keys * 1) "key67" 2) "key41" 3) "key30" 4) "key23"....192.168.100.161:6379> get key21"value21"192.168.100.161:6379> get key22(error) MOVED 9163 192.168.100.162:6379
----slave只能存数据，不能读，读需要在对应槽位的master节点----root@redis-server4:~# redis-cli -h 192.168.100.164 -a q1w2e3r4ys@123192.168.100.164:6379> keys * 1) "key67" 2) "key41" 3) "key30"....192.168.100.164:6379> get key67(error) MOVED 16298 192.168.100.163:6379192.168.100.164:6379> get key41(error) MOVED 14606 192.168.100.163:6379
root@redis-server4:~# redis-cli -a q1w2e3r4ys@123 --no-auth-warning --cluster info 192.168.100.161:6379192.168.100.161:6379 (d80786f3...) -> 33 keys | 5461 slots | 1 slaves.192.168.100.163:6379 (ab91069f...) -> 37 keys | 5461 slots | 1 slaves.192.168.100.162:6379 (7e0d980b...) -> 32 keys | 5462 slots | 1 slaves.[OK] 102 keys in 3 masters.0.01 keys per slot on average.
root@redis-server1:~# redis-cli -a q1w2e3r4ys@123 --cluster call 192.168.100.161:6379 dbsizeWarning: Using a password with '-a' or '-u' option on the command line interface may not be safe.>>> Calling dbsize192.168.100.161:6379: 32192.168.100.166:6379: 32192.168.100.165:6379: 32192.168.100.164:6379: 36192.168.100.163:6379: 36192.168.100.162:6379: 32
----创建一个自动写数据脚本----root@redis-server8:~# vi redis-client.sh#!/bin/bash#Author: ZhangJieNUM=`seq 1 100000`for i in ${NUM};do redis-cli -h 127.0.0.1 -a q1w2e3r4ys@123 set key-${i} value-${i} echo "key-${i} value-${i} 写入完成"doneecho "十万个key写入到Redis完成"
----执行脚本，写入数据----root@redis-server8:~# bash redis-client.sh....key-99998 value-99998 写入完成Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.OKkey-99999 value-99999 写入完成Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.OKkey-100000 value-100000 写入完成十万个key写入到Redis完成
root@redis-server8:~# cd /usr/local/src/root@redis-server8:/usr/local/src# wget https://github.com/tair-opensource/RedisShake/releases/download/v4.0.0/redis-shake-linux-amd64.tar.gzroot@redis-server8:/usr/local/src# tar xvf redis-shake-linux-amd64.tar.gz
root@redis-server8:/usr/local/src# vi shake.tomlfunction = ""[sync_reader] #读取数据的配置=源主机cluster = falseaddress = "192.168.100.168:6379"username = "" # keep empty if not using ACLpassword = "q1w2e3r4ys@123" # keep empty if no authentication is requiredtls = false[redis_writer] #写数据的配置=⽬的主机cluster = true #是否是集群模式address = "192.168.100.161:6379"username = "" # keep empty if not using ACLpassword = "q1w2e3r4ys@123" # keep empty if no authentication is requiredtls = false[advanced]dir = "data"ncpu = 0 # runtime.GOMAXPROCS, 0 means use runtime.NumCPU() cpu corespprof_port = 0 # pprof port, 0 means disablestatus_port = 0 # status port, 0 means disable# loglog_file = "shake.log"log_level = "info" # debug, info or warnlog_interval = 5 # in secondsrdb_restore_command_behavior = "panic" # panic, rewrite or skippipeline_count_limit = 1024target_redis_client_max_querybuf_len = 1024_000_000target_redis_proto_max_bulk_len = 512_000_000aws_psync = "" # example: aws_psync = "10.0.0.1:6379@nmfu2sl5osync,10.0.0.1:6379@xhma21xfkssync"
root@redis-server8:/usr/local/src# ./redis-shake shake.toml2023-09-13 08:23:12 INF load config from file: shake.toml2023-09-13 08:23:12 INF log_level: [info], log_file: [/usr/local/src/data/shake.log]2023-09-13 08:23:12 INF changed work dir to [/usr/local/src/data]2023-09-13 08:23:12 INF GOMAXPROCS defaults to the value of runtime.NumCPU [2]2023-09-13 08:23:12 INF not set pprof port2023-09-13 08:23:12 INF no function script2023-09-13 08:23:12 INF create SyncStandaloneReader: 192.168.100.168:63792023-09-13 08:23:12 INF redisClusterWriter load cluster nodes. line=d80786f363c7e2c8664e69b4fab47cbd7417dbe4 192.168.100.161:6379@16379 myself,master - 0 1694593390000 1 connected 0-54602023-09-13 08:23:12 INF redisClusterWriter load cluster nodes. line=ab91069f9d0a4773d857119c6cc3bd29db6c0552 192.168.100.163:6379@16379 master - 0 1694593391631 3 connected 10923-163832023-09-13 08:23:12 INF redisClusterWriter load cluster nodes. line=7e0d980b0f2d067ec797a9b76cecde50f532844a 192.168.100.162:6379@16379 master - 0 1694593389000 2 connected 5461-109222023-09-13 08:23:12 INF redisClusterWriter connected to redis cluster successful. addresses=[192.168.100.161:6379 192.168.100.163:6379 192.168.100.162:6379]2023-09-13 08:23:12 INF create RedisClusterWriter: 192.168.100.161:63792023-09-13 08:23:12 INF not set status port2023-09-13 08:23:12 INF start syncing...2023-09-13 08:23:17 INF read_count=[100000], read_ops=[868.16], write_count=[100000], write_ops=[869.16], syncing aof, diff=[100000]2023-09-13 08:23:22 INF read_count=[100000], read_ops=[0.00], write_count=[100000], write_ops=[0.00], syncing aof, diff=[0]2023-09-13 08:23:27 INF read_count=[100000], read_ops=[0.00], write_count=[100000], write_ops=[0.00], syncing aof, diff=[0]2023-09-13 08:23:32 INF read_count=[100000], read_ops=[0.00], write_count=[100000], write_ops=[0.00], syncing aof, diff=[0]
root@redis-server8:/var/www/html# redis-cli -h 192.168.100.168 -a q1w2e3r4ys@123Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.192.168.100.168:6379> keys *1) "testKey"192.168.100.168:6379> keys *1) "qbn"2) "testKey"192.168.100.168:6379> get qbn"a:5:{i:0;a:3:{s:10:\"product_id\";s:1:\"1\";s:12:\"product_name\";s:23:\"Virtual Private Servers\";s:5:\"price\";s:1:\"5\";}i:1;a:3:{s:10:\"product_id\";s:1:\"2\";s:12:\"product_name\";s:17:\"Managed Databases\";s:5:\"price\";s:2:\"15\";}i:2;a:3:{s:10:\"product_id\";s:1:\"3\";s:12:\"product_name\";s:13:\"Block Storage\";s:5:\"price\";s:2:\"10\";}i:3;a:3:{s:10:\"product_id\";s:1:\"4\";s:12:\"product_name\";s:18:\"Managed Kubernetes\";s:5:\"price\";s:2:\"60\";}i:4;a:3:{s:10:\"product_id\";s:1:\"5\";s:12:\"product_name\";s:13:\"Load Balancer\";s:5:\"price\";s:2:\"10\";}}"192.168.100.168:6379> ttl qbn #我们设置了60s的过期时间，所以key只能保存60秒(integer) 47192.168.100.168:6379> ttl qbn(integer) 46192.168.100.168:6379> ttl qbn(integer) 44
root@redis-server7:~# vi /apps/redis/etc/redis.conf....cluster-enabled yescluster-config-file nodes-6379.conmasterauth q1w2e3r4ys@123....root@redis-server8:~# vi /apps/redis/etc/redis.conf....cluster-enabled yescluster-config-file nodes-6379.conmasterauth q1w2e3r4ys@123....root@redis-server7:~# systemctl restart redis.serviceroot@redis-server8:~# systemctl restart redis.service
----查看使用说明----root@redis-server7:~# redis-cli --cluster help add-node new_host:new_port existing_host:existing_port #格式为：新节点:集群已经存在的节点 --cluster-slave --cluster-master-id <arg>#添加的新redis节点IP和端⼝，新的node节点加到集群之后默认是master节点，但是没有slots数据，需要重新分配。----验证数据是否是空的----root@redis-server8:~# redis-cli -h 192.168.100.167 -a q1w2e3r4ys@123 --no-auth-warning192.168.100.167:6379> keys *(empty array)root@redis-server8:~# redis-cli -h 192.168.100.168 -a q1w2e3r4ys@123 --no-auth-warning192.168.100.168:6379> keys *(empty array)----将节点192.168.100.167:6379 添加到⽬的集群192.168.100.161:6379----root@redis-server8:~# redis-cli -a q1w2e3r4ys@123 --cluster add-node 192.168.100.167:6379 192.168.100.161:6379>>> Adding node 192.168.100.167:6379 to cluster 192.168.100.161:6379>>> Performing Cluster Check (using node 192.168.100.161:6379)M: d80786f363c7e2c8664e69b4fab47cbd7417dbe4 192.168.100.161:6379 slots:[0-5460] (5461 slots) master 1 additional replica(s)S: d18c35eaaa7db9d0f9e0223ccf95aa834ab9ca4e 192.168.100.166:6379 slots: (0 slots) slave replicates 7e0d980b0f2d067ec797a9b76cecde50f532844aS: 1466ec80241f619bf11c729c166c8dadbce0df74 192.168.100.165:6379 slots: (0 slots) slave replicates d80786f363c7e2c8664e69b4fab47cbd7417dbe4S: 4b5028a691c29d4d7964b02dcc07e30c7dc419fe 192.168.100.164:6379 slots: (0 slots) slave replicates ab91069f9d0a4773d857119c6cc3bd29db6c0552M: ab91069f9d0a4773d857119c6cc3bd29db6c0552 192.168.100.163:6379 slots:[10923-16383] (5461 slots) master 1 additional replica(s)M: 7e0d980b0f2d067ec797a9b76cecde50f532844a 192.168.100.162: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.>>> Getting functions from cluster>>> Send FUNCTION LIST to 192.168.100.167:6379 to verify there is no functions in it>>> Send FUNCTION RESTORE to 192.168.100.167:6379>>> Send CLUSTER MEET to node 192.168.100.167:6379 to make it join the cluster.[OK] New node added correctly.
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.>>> Performing Cluster Check (using node 192.168.100.161:6379)M: d80786f363c7e2c8664e69b4fab47cbd7417dbe4 192.168.100.161:6379 #⽬的主机ID slots:[1365-5460] (4096 slots) master 1 additional replica(s)M: a458282fde42f63d4c5e18be5a17ea7b47025273 192.168.100.167:6379 #源主机ID（下架主机） slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master 1 additional replica(s)S: d18c35eaaa7db9d0f9e0223ccf95aa834ab9ca4e 192.168.100.166:6379 slots: (0 slots) slave replicates 7e0d980b0f2d067ec797a9b76cecde50f532844aS: 9d8d562e4cc5fc632cd05d44e51cc3f70eee682a 192.168.100.168:6379 slots: (0 slots) slave replicates a458282fde42f63d4c5e18be5a17ea7b47025273S: 1466ec80241f619bf11c729c166c8dadbce0df74 192.168.100.165:6379 slots: (0 slots) slave replicates d80786f363c7e2c8664e69b4fab47cbd7417dbe4S: 4b5028a691c29d4d7964b02dcc07e30c7dc419fe 192.168.100.164:6379 slots: (0 slots) slave replicates ab91069f9d0a4773d857119c6cc3bd29db6c0552M: ab91069f9d0a4773d857119c6cc3bd29db6c0552 192.168.100.163:6379 slots:[12288-16383] (4096 slots) master 1 additional replica(s)M: 7e0d980b0f2d067ec797a9b76cecde50f532844a 192.168.100.162:6379 slots:[6827-10922] (4096 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)? 4096 #需要分配的槽位数What is the receiving node ID? d80786f363c7e2c8664e69b4fab47cbd7417dbe4 #分配的⽬的master主机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: a458282fde42f63d4c5e18be5a17ea7b47025273 #从哪个源主机分配Source node #2: done #完成.... Moving slot 12285 from a458282fde42f63d4c5e18be5a17ea7b47025273 Moving slot 12286 from a458282fde42f63d4c5e18be5a17ea7b47025273 Moving slot 12287 from a458282fde42f63d4c5e18be5a17ea7b47025273Do you want to proceed with the proposed reshard plan (yes/no)? yes #确认分配Moving slot 0 from 192.168.100.167:6379 to 192.168.100.161:6379:Moving slot 1 from 192.168.100.167:6379 to 192.168.100.161:6379:Moving slot 2 from 192.168.100.167:6379 to 192.168.100.161:6379:....
----验证集群主机状态----root@redis-server1:~# redis-cli -a q1w2e3r4ys@123 --cluster check 192.168.100.161:6379Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.192.168.100.161:6379 (d80786f3...) -> 50 keys | 8192 slots | 3 slaves.192.168.100.163:6379 (ab91069f...) -> 25 keys | 4096 slots | 1 slaves.192.168.100.162:6379 (7e0d980b...) -> 25 keys | 4096 slots | 1 slaves.[OK] 100 keys in 3 masters.0.01 keys per slot on average.>>> Performing Cluster Check (using node 192.168.100.161:6379)M: d80786f363c7e2c8664e69b4fab47cbd7417dbe4 192.168.100.161:6379 slots:[0-6826],[10923-12287] (8192 slots) master 3 additional replica(s)S: a458282fde42f63d4c5e18be5a17ea7b47025273 192.168.100.167:6379 #slave⻆⾊ slots: (0 slots) slave replicates d80786f363c7e2c8664e69b4fab47cbd7417dbe4S: d18c35eaaa7db9d0f9e0223ccf95aa834ab9ca4e 192.168.100.166:6379 slots: (0 slots) slave replicates 7e0d980b0f2d067ec797a9b76cecde50f532844aS: 9d8d562e4cc5fc632cd05d44e51cc3f70eee682a 192.168.100.168:6379 #slave⻆⾊ slots: (0 slots) slave replicates d80786f363c7e2c8664e69b4fab47cbd7417dbe4S: 1466ec80241f619bf11c729c166c8dadbce0df74 192.168.100.165:6379 slots: (0 slots) slave replicates d80786f363c7e2c8664e69b4fab47cbd7417dbe4S: 4b5028a691c29d4d7964b02dcc07e30c7dc419fe 192.168.100.164:6379 slots: (0 slots) slave replicates ab91069f9d0a4773d857119c6cc3bd29db6c0552M: ab91069f9d0a4773d857119c6cc3bd29db6c0552 192.168.100.163:6379 slots:[12288-16383] (4096 slots) master 1 additional replica(s)M: 7e0d980b0f2d067ec797a9b76cecde50f532844a 192.168.100.162:6379 slots:[6827-10922] (4096 slots) master 1 additional replica(s)[OK] All nodes agree about slots configuration.
root@redis-server1:~# redis-cli -a q1w2e3r4ys@123 --cluster del-node 192.168.100.167:6379 a458282fde42f63d4c5e18be5a17ea7b47025273>>> Removing node a458282fde42f63d4c5e18be5a17ea7b47025273 from cluster 192.168.100.167:6379>>> Sending CLUSTER FORGET messages to the cluster...>>> Sending CLUSTER RESET SOFT to the deleted node.root@redis-server1:~# redis-cli -a q1w2e3r4ys@123 --cluster del-node 192.168.100.168:6379 9d8d562e4cc5fc632cd05d44e51cc3f70eee682a>>> Removing node 9d8d562e4cc5fc632cd05d44e51cc3f70eee682a from cluster 192.168.100.168:6379>>> Sending CLUSTER FORGET messages to the cluster...>>> Sending CLUSTER RESET SOFT to the deleted node.
root@redis-server1:~# redis-cli -a q1w2e3r4ys@123 --cluster check 192.168.100.161:6379Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.192.168.100.161:6379 (d80786f3...) -> 50 keys | 8192 slots | 1 slaves. #槽位太多，需要重新平衡一下192.168.100.163:6379 (ab91069f...) -> 25 keys | 4096 slots | 1 slaves.192.168.100.162:6379 (7e0d980b...) -> 25 keys | 4096 slots | 1 slaves.[OK] 100 keys in 3 masters.0.01 keys per slot on average.>>> Performing Cluster Check (using node 192.168.100.161:6379)M: d80786f363c7e2c8664e69b4fab47cbd7417dbe4 192.168.100.161:6379 slots:[0-6826],[10923-12287] (8192 slots) master 1 additional replica(s)S: d18c35eaaa7db9d0f9e0223ccf95aa834ab9ca4e 192.168.100.166:6379 slots: (0 slots) slave replicates 7e0d980b0f2d067ec797a9b76cecde50f532844aS: 1466ec80241f619bf11c729c166c8dadbce0df74 192.168.100.165:6379 slots: (0 slots) slave replicates d80786f363c7e2c8664e69b4fab47cbd7417dbe4S: 4b5028a691c29d4d7964b02dcc07e30c7dc419fe 192.168.100.164:6379 slots: (0 slots) slave replicates ab91069f9d0a4773d857119c6cc3bd29db6c0552M: ab91069f9d0a4773d857119c6cc3bd29db6c0552 192.168.100.163:6379 slots:[12288-16383] (4096 slots) master 1 additional replica(s)M: 7e0d980b0f2d067ec797a9b76cecde50f532844a 192.168.100.162:6379 slots:[6827-10922] (4096 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@redis-server1:~# redis-cli -a q1w2e3r4ys@123 --cluster check 192.168.100.161:6379Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.192.168.100.161:6379 (d80786f3...) -> 50 keys | 8192 slots | 1 slaves.192.168.100.163:6379 (ab91069f...) -> 25 keys | 4096 slots | 1 slaves.192.168.100.162:6379 (7e0d980b...) -> 25 keys | 4096 slots | 1 slaves.[OK] 100 keys in 3 masters.0.01 keys per slot on average.>>> Performing Cluster Check
----验证槽位状态----root@redis-server1:~# redis-cli -a q1w2e3r4ys@123 --cluster check 192.168.100.161:6379Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.192.168.100.161:6379 (d80786f3...) -> 37 keys | 5461 slots | 1 slaves.192.168.100.163:6379 (ab91069f...) -> 32 keys | 5462 slots | 1 slaves.192.168.100.162:6379 (7e0d980b...) -> 31 keys | 5461 slots | 1 slaves.[OK] 100 keys in 3 masters.0.01 keys per slot on average.>>> Performing Cluster Check (using node 192.168.100.161:6379)M: d80786f363c7e2c8664e69b4fab47cbd7417dbe4 192.168.100.161:6379 slots:[2731-6826],[10923-12287] (5461 slots) master 1 additional replica(s)S: d18c35eaaa7db9d0f9e0223ccf95aa834ab9ca4e 192.168.100.166:6379 slots: (0 slots) slave replicates 7e0d980b0f2d067ec797a9b76cecde50f532844aS: 1466ec80241f619bf11c729c166c8dadbce0df74 192.168.100.165:6379 slots: (0 slots) slave replicates d80786f363c7e2c8664e69b4fab47cbd7417dbe4S: 4b5028a691c29d4d7964b02dcc07e30c7dc419fe 192.168.100.164:6379 slots: (0 slots) slave replicates ab91069f9d0a4773d857119c6cc3bd29db6c0552M: ab91069f9d0a4773d857119c6cc3bd29db6c0552 192.168.100.163:6379 slots:[0-1365],[12288-16383] (5462 slots) master 1 additional replica(s)M: 7e0d980b0f2d067ec797a9b76cecde50f532844a 192.168.100.162:6379 slots:[1366-2730],[6827-10922] (5461 slots) master 1 additional replica(s)
