Docker | redis集群部署实战( 二 ) _生活百科

赋予start_redis_script.sh文件可执行权限[root@--- ~]# chmod o+x start_redis_script.sh执行脚本，启动redis容器服务./start_redis_script.sh

文章插图
查看redis容器

[root@--- var]# docker psCONTAINER IDIMAGECOMMANDCREATEDSTATUSPORTSNAMES0d3c18b61098redis:5.0.9-alpine3.11"docker-entrypoint.s…"2 seconds agoUp 1 second0.0.0.0:6376->6379/tcp, 0.0.0.0:16376->16379/tcpredis-6ee896fb093daredis:5.0.9-alpine3.11"docker-entrypoint.s…"13 seconds agoUp 12 seconds0.0.0.0:6375->6379/tcp, 0.0.0.0:16375->16379/tcpredis-5a83bb7b16dffredis:5.0.9-alpine3.11"docker-entrypoint.s…"48 seconds agoUp 47 seconds0.0.0.0:6374->6379/tcp, 0.0.0.0:16374->16379/tcpredis-4ffe4c9619bedredis:5.0.9-alpine3.11"docker-entrypoint.s…"58 seconds agoUp 57 seconds0.0.0.0:6373->6379/tcp, 0.0.0.0:16373->16379/tcpredis-3a316a31e273fredis:5.0.9-alpine3.11"docker-entrypoint.s…"About a minute agoUp About a minute0.0.0.0:6372->6379/tcp, 0.0.0.0:16372->16379/tcpredis-271c072f57c29redis:5.0.9-alpine3.11"docker-entrypoint.s…"9 minutes agoUp 9 minutes0.0.0.0:6371->6379/tcp, 0.0.0.0:16371->16379/tcpredis-1[root@--- var]#

创建集群进入任意一个 Redis 实例
进入redis-1容器docker exec -it redis-1 /bin/sh创建集群主节点

Redis Cluster最低要求是3个主节点
--cluster-replicas 参数为数字，1表示每个主节点需要1个从节点。

# redis-1 容器内/data # redis-cli --cluster create 172.38.0.11:6379 172.38.0.12:6379 172.38.0.13:6379 172.38.0.14:6379 172.38.0.15:6379 172.38.0.16:6379 --cluster-replicas 1

文章插图
测试连接集群连接集群 -c# redis-1 容器内/data # redis-cli -c127.0.0.1:6379>查看集群信息 cluster info

127.0.0.1:6379> cluster infocluster_state:okcluster_slots_assigned:16384cluster_slots_ok:16384cluster_slots_pfail:0cluster_slots_fail:0cluster_known_nodes:6cluster_size:3cluster_current_epoch:6cluster_my_epoch:1cluster_stats_messages_ping_sent:292cluster_stats_messages_pong_sent:307cluster_stats_messages_sent:599cluster_stats_messages_ping_received:302cluster_stats_messages_pong_received:292cluster_stats_messages_meet_received:5cluster_stats_messages_received:599127.0.0.1:6379>

查看节点信息 cluster nodes

127.0.0.1:6379> cluster nodesb3f737d0d77b823794087011f1501fd43a2ea316 172.38.0.12:6379@16379 master - 0 1633332452560 2 connected 5461-10922506ff2bf1020d468e7d7a81ddbfb616a7e9b7d96 172.38.0.13:6379@16379 master - 0 1633332453000 3 connected 10923-163837f57f8a01493fa9e46e24ad8a9e46995634f7442 172.38.0.15:6379@16379 slave 70ebdca0264c079bb2c33452e6388d37706da282 0 1633332453000 5 connected70ebdca0264c079bb2c33452e6388d37706da282 172.38.0.11:6379@16379 myself,master - 0 1633332452000 1 connected 0-5460f839b6924977e99d3b74324f2ef70b3678e1a257 172.38.0.14:6379@16379 slave 506ff2bf1020d468e7d7a81ddbfb616a7e9b7d96 0 1633332453762 4 connectedbbc4dd0639b90e9ddfb5cef278be04a24276cbdb 172.38.0.16:6379@16379 slave b3f737d0d77b823794087011f1501fd43a2ea316 0 1633332453000 6 connected127.0.0.1:6379>

文章插图
测试主从节点替换【Docker | redis集群部署实战】验证高可用
set一个值，然后停掉对应的服务，再次get，验证是否可以得到值
set值127.0.0.1:6379> set a b-> Redirected to slot [15495] located at 172.38.0.13:6379OK172.38.0.13:6379>发现a值设置在了172.38.0.13容器上，然后我们试着去停掉redis-3容器的服务，然后再次get,看一下结果
get值172.38.0.13:6379> get a"b"172.38.0.13:6379>停止redis-3容器里的redis服务docker stop redis-3再次取值

172.38.0.13:6379> get aCould not connect to Redis at 172.38.0.13:6379: Host is unreachable(34.04s)not connected> exit# 重连集群/data # redis-cli -c127.0.0.1:6379> get a-> Redirected to slot [15495] located at 172.38.0.14:6379"b"172.38.0.14:6379>

发现a值被存储到了172.38.0.14机器上，172.38.0.14是172.38.0.13的从节点，当主节点172.38.0.13发生故障时，自动替换到172.38.0.13，这就是高可用
查看redis节点服务信息发现172.38.0.13节点fail, 172.38.0.14变成master