部署redis集群

11 篇文章 0 订阅

实战:部署redis集群

#首先创建redis网络
[root@node1 docker]#  docker network create --subnet 172.38.0.0/16 redis
3c72a2b7dd46f17816f590b4d159b4c75ec4979c0fac8551b8b8a9868c7365db
[root@node1 docker]# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
9b937167a279        bin_default         bridge              local
6aae8ccbba9d        bridge              bridge              local
e118e3656a14        docker_default      bridge              local
98096ab0c7e7        harbor_harbor       bridge              local
201680a6b52b        host                host                local
e275e6bfa5cf        mynet               bridge              local
6da132137731        none                null                local
3c72a2b7dd46        redis               bridge              local
#bai'n
[root@node1 docker]# for port in $(seq 1 6); \
> do \
> mkdir -p /mydata/redis/node-${port}/conf
> touch /mydata/redis/node-${port}/conf/redis.conf
> cat << EOF > /mydata/redis/node-${port}/conf/redis.conf
> port 6379
> cluster-enable yes
> cluster-config-file nodes_conf
> cluster-node-timeout 5000
> cluster-announce-ip 172.38.0.1${port}
> cluster-announce-port 6379
> cluster-announce-bus-port 6379
> appendonly yes
> EOF
> done

redis创建配置文件脚本内容

for port in $(seq 1 6); \
do \
mkdir -p /mydata/redis/node-${port}/conf
touch /mydata/redis/node-${port}/conf/redis.conf
cat << EOF > /mydata/redis/node-${port}/conf/redis.conf
port 6379
bind 0.0.0.0
cluster-enabled yes
cluster-config-file nodes.conf
cluster-node-timeout 5000
cluster-announce-ip 172.38.0.1${port}
cluster-announce-port 6379
cluster-announce-bus-port 16379
appendonly yes
EOF
done

redis批量启动脚本

for port in $(seq 1 6); \
do \
docker run -p 637${port}:6379 -p 1637${port}:16379 --name redis-${port} \
-v /mydata/redis/node-${port}/data:/data \
-v /mydata/redis/node-${port}/conf/redis.conf:/etc/redis/redis.conf \
-d --net redis --ip 172.38.0.1${port} redis:5.0.9-alpine3.11 redis-server /etc/redis/redis.conf;
done

然后启动redis容器,这里需要启动6个redis容器

#第一个redis直接使用命令启动
[root@node1 docker]# docker run -p 6371:6379 -p 16371:16379 --name redis-1 \
> -v /mydata/redis/node-1/data:/data \
> -v /mydata/redis/node-1/conf/redis.conf:/etc/redis/redis.conf \
> -d --net redis --ip 172.38.0.11 redis:5.0.9-alpine3.11 redis-server /etc/redis/redis.conf
c8d26544ad5d22401beb82f2f4fc0a2d9a6a4ebd4d3410625c998cc701cab028
#启动成功,查看状态
[root@node1 docker]# docker ps
CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS                                              NAMES
c8d26544ad5d        redis:5.0.9-alpine3.11   "docker-entrypoint..."   5 seconds ago       Up 4 seconds        0.0.0.0:6371->6379/tcp, 0.0.0.0:16371->16379/tcp   redis-1
#第二至六个容器,使用脚本启动
[root@node1 docker]# for port in $(seq 2 6); \
> do \
> docker run -p 637${port}:6379 -p 1637${port}:16379 --name redis-${port} \
> -v /mydata/redis/node-${port}/data:/data \
> -v /mydata/redis/node-${port}/conf/redis.conf:/etc/redis/redis.conf \
> -d --net redis --ip 172.38.0.1${port} redis:5.0.9-alpine3.11 redis-server /etc/redis/redis.conf;
> done
b9818abea6c4663f8e8f3573b56dd2207d0e91d887096237ec8692f4b7de811c
24ef6937a686354495eea557bc82642b75a98823e7b9f1301864ac1cdb50c442
20ff7556686b1a2d78339cca23b3af52f2db0357386e9363525b30a8c01d5c63
e0d00235f2c5bb35e615f0a8c645cd410f691f0435518704f6550653faa23b2f
9ffb0b18abcfa81f0ac342175e8b973bc2cb38e69ce73b4a425aa386cddcd46a
#启动成功,查看状态, 都启动成功
[root@node1 docker]# docker ps
CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS                                              NAMES
9ffb0b18abcf        redis:5.0.9-alpine3.11   "docker-entrypoint..."   2 seconds ago       Up 2 seconds        0.0.0.0:6376->6379/tcp, 0.0.0.0:16376->16379/tcp   redis-6
e0d00235f2c5        redis:5.0.9-alpine3.11   "docker-entrypoint..."   3 seconds ago       Up 2 seconds        0.0.0.0:6375->6379/tcp, 0.0.0.0:16375->16379/tcp   redis-5
20ff7556686b        redis:5.0.9-alpine3.11   "docker-entrypoint..."   3 seconds ago       Up 2 seconds        0.0.0.0:6374->6379/tcp, 0.0.0.0:16374->16379/tcp   redis-4
24ef6937a686        redis:5.0.9-alpine3.11   "docker-entrypoint..."   3 seconds ago       Up 3 seconds        0.0.0.0:6373->6379/tcp, 0.0.0.0:16373->16379/tcp   redis-3
b9818abea6c4        redis:5.0.9-alpine3.11   "docker-entrypoint..."   4 seconds ago       Up 3 seconds        0.0.0.0:6372->6379/tcp, 0.0.0.0:16372->16379/tcp   redis-2
c8d26544ad5d        redis:5.0.9-alpine3.11   "docker-entrypoint..."   38 seconds ago      Up 37 seconds       0.0.0.0:6371->6379/tcp, 0.0.0.0:16371->16379/tcp   redis-1
# 进入任一redis, 注意redis命令是/bin/sh, 不是bash
[root@node1 docker]# docker exec -it redis-1 /bin/sh
#默认目录是/data
/data # ls
appendonly.aof  nodes.conf
# 创建redis 集群
/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
>>> Performing hash slots allocation on 6 nodes...
Master[0] -> Slots 0 - 5460
Master[1] -> Slots 5461 - 10922
Master[2] -> Slots 10923 - 16383
Adding replica 172.38.0.15:6379 to 172.38.0.11:6379
Adding replica 172.38.0.16:6379 to 172.38.0.12:6379
Adding replica 172.38.0.14:6379 to 172.38.0.13:6379
M: 7e593624e546539f83c844a5d0014fc5687aa6c4 172.38.0.11:6379
   slots:[0-5460] (5461 slots) master
M: 586370b79f1be2968d847f5947819e632da66aa1 172.38.0.12:6379
   slots:[5461-10922] (5462 slots) master
M: 32026a285df860992a1a7dac4e9e1d60f253decd 172.38.0.13:6379
   slots:[10923-16383] (5461 slots) master
S: 21ea6b6ac1b6e238bebad3ac54ac72a0274ecae0 172.38.0.14:6379
   replicates 32026a285df860992a1a7dac4e9e1d60f253decd
S: 383e7f0fd8aab86bd45740de3a1a2ad5681eb591 172.38.0.15:6379
   replicates 7e593624e546539f83c844a5d0014fc5687aa6c4
S: d37dd99e5ddb19d9961ce1d613a93adbf00e25d0 172.38.0.16:6379
   replicates 586370b79f1be2968d847f5947819e632da66aa1
Can I set the above configuration? (type 'yes' to accept): yes
>>> Nodes configuration updated
>>> Assign a different config epoch to each node
>>> Sending CLUSTER MEET messages to join the cluster
Waiting for the cluster to join
...
>>> Performing Cluster Check (using node 172.38.0.11:6379)
M: 7e593624e546539f83c844a5d0014fc5687aa6c4 172.38.0.11:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 383e7f0fd8aab86bd45740de3a1a2ad5681eb591 172.38.0.15:6379
   slots: (0 slots) slave
   replicates 7e593624e546539f83c844a5d0014fc5687aa6c4
S: d37dd99e5ddb19d9961ce1d613a93adbf00e25d0 172.38.0.16:6379
   slots: (0 slots) slave
   replicates 586370b79f1be2968d847f5947819e632da66aa1
S: 21ea6b6ac1b6e238bebad3ac54ac72a0274ecae0 172.38.0.14:6379
   slots: (0 slots) slave
   replicates 32026a285df860992a1a7dac4e9e1d60f253decd
M: 32026a285df860992a1a7dac4e9e1d60f253decd 172.38.0.13:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
M: 586370b79f1be2968d847f5947819e632da66aa1 172.38.0.12: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.
# 进入redis集群,并查看集群信息
/data # redis-cli -c
127.0.0.1:6379> cluster info
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:6
cluster_size:3
cluster_current_epoch:6
cluster_my_epoch:1
cluster_stats_messages_ping_sent:236
cluster_stats_messages_pong_sent:233
cluster_stats_messages_sent:469
cluster_stats_messages_ping_received:228
cluster_stats_messages_pong_received:236
cluster_stats_messages_meet_received:5
cluster_stats_messages_received:469
#查看集群节点
127.0.0.1:6379> cluster nodes
383e7f0fd8aab86bd45740de3a1a2ad5681eb591 172.38.0.15:6379@16379 slave 7e593624e546539f83c844a5d0014fc5687aa6c4 0 1612059041000 5 connected
d37dd99e5ddb19d9961ce1d613a93adbf00e25d0 172.38.0.16:6379@16379 slave 586370b79f1be2968d847f5947819e632da66aa1 0 1612059041568 6 connected
21ea6b6ac1b6e238bebad3ac54ac72a0274ecae0 172.38.0.14:6379@16379 slave 32026a285df860992a1a7dac4e9e1d60f253decd 0 1612059041266 4 connected
7e593624e546539f83c844a5d0014fc5687aa6c4 172.38.0.11:6379@16379 myself,master - 0 1612059041000 1 connected 0-5460
32026a285df860992a1a7dac4e9e1d60f253decd 172.38.0.13:6379@16379 master - 0 1612059040057 3 connected 10923-16383
586370b79f1be2968d847f5947819e632da66aa1 172.38.0.12:6379@16379 master - 0 1612059040763 2 connected 5461-10922
#集群可用性测试
127.0.0.1:6379> set a b
-> Redirected to slot [15495] located at 172.38.0.13:6379
OK
#数据在节点172.38.0.13
# get 数据正常
172.38.0.13:6379> get a
"b"
#停止节点172.38.0.13,验证集群高可用性
[root@node1 docker]# docker stop redis-3
redis-3
#重新进入集群测试
/data # redis-cli -c
127.0.0.1:6379> get a
-> Redirected to slot [15495] located at 172.38.0.14:6379
"b"
#发现数据从节点172.38.0.14获取到,再看集群nodes 发现:172.38.0.13:failed, 而172.38.0.14变成master
172.38.0.14:6379> cluster nodes
21ea6b6ac1b6e238bebad3ac54ac72a0274ecae0 172.38.0.14:6379@16379 myself,master - 0 1612059556000 7 connected 10923-16383
383e7f0fd8aab86bd45740de3a1a2ad5681eb591 172.38.0.15:6379@16379 slave 7e593624e546539f83c844a5d0014fc5687aa6c4 0 1612059555890 5 connected
32026a285df860992a1a7dac4e9e1d60f253decd 172.38.0.13:6379@16379 master,fail - 1612059496236 1612059494000 3 connected
7e593624e546539f83c844a5d0014fc5687aa6c4 172.38.0.11:6379@16379 master - 0 1612059555000 1 connected 0-5460
586370b79f1be2968d847f5947819e632da66aa1 172.38.0.12:6379@16379 master - 0 1612059555000 2 connected 5461-10922
d37dd99e5ddb19d9961ce1d613a93adbf00e25d0 172.38.0.16:6379@16379 slave 586370b79f1be2968d847f5947819e632da66aa1 0 1612059556594 6 connected
172.38.0.14:6379> 

至此,redis集群搭建完成。

***************用努力照亮现实的梦!***********************

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值