Docker（redis集群）

已于 2022-11-14 12:01:42 修改
阅读量1.1k 收藏 1
点赞数 3
文章标签： docker redis 容器
于 2022-11-10 11:37:11 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_38380811/article/details/127782956
版权

文章目录

一、搭建3主3从redis集群

redis集群中至少3个主节点

1、准备6台redis节点的数据卷挂载路径

[root@localhost redis]# ll
drwxr-xr-x. 3 systemd-coredump root 92 Nov 13 17:09 redis-node-1
drwxr-xr-x. 3 systemd-coredump root 36 Nov 13 17:09 redis-node-2
drwxr-xr-x. 3 systemd-coredump root 36 Nov 13 17:10 redis-node-3
drwxr-xr-x. 3 systemd-coredump root 36 Nov 13 17:10 redis-node-4
drwxr-xr-x. 3 systemd-coredump root 36 Nov 13 17:11 redis-node-5
drwxr-xr-x. 3 systemd-coredump root 36 Nov 13 17:12 redis-node-6

2、创建6台redis节点挂载的外部配置文件

[root@localhost redis-node-1]# pwd
/redis/redis-node-1
[root@localhost redis-node-1]# ll
-rw-r--r--. 1 root             root  63285 Nov 13 17:02 redis.conf

redis.conf配置文件如下：将每一台的redis节点配置文件的端口号修改对应

[root@localhost redis-node-1]# vim redis.conf

protected-mode no
port 6379
tcp-backlog 511
timeout 0
tcp-keepalive 300
daemonize no
supervised no
pidfile /var/run/redis_6379.pid
loglevel notice
logfile ""
databases 16
always-show-logo yes
save 900 1
save 300 10
save 60 10000
stop-writes-on-bgsave-error yes
rdbcompression yes
rdbchecksum yes
dbfilename dump.rdb
dir ./
replica-serve-stale-data yes
replica-read-only yes
repl-diskless-sync-delay 5
repl-disable-tcp-nodelay no
replica-priority 100
lazyfree-lazy-eviction no
lazyfree-lazy-expire no
lazyfree-lazy-server-del no
replica-lazy-flush no
appendonly no
appendfilename "appendonly.aof"
no-appendfsync-on-rewrite no
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
aof-load-truncated yes
aof-use-rdb-preamble yes
lua-time-limit 5000
slowlog-log-slower-than 10000
slowlog-max-len 128
notify-keyspace-events Ex
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
list-max-ziplist-size -2
list-compress-depth 0
set-max-intset-entries 512
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
hll-sparse-max-bytes 3000
stream-node-max-bytes 4096
stream-node-max-entries 100
activerehashing yes
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit replica 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
hz 10
dynamic-hz yes
aof-rewrite-incremental-fsync yes
rdb-save-incremental-fsync yes

3、创建六个redis容器

[root@localhost tomcatData]# docker run -d --name redis-node-1 --net host --privileged=true -v /redis/redis-node-1:/data redis --cluster-enabled yes --appendonly yes --port 6379
7f597842ac768d5d25124f560a1fd07488b29c44b2d7bf35560701ad52157aa6
[root@localhost tomcatData]# docker run -d --name redis-node-2 --net host --privileged=true -v /redis/redis-node-2:/data redis --cluster-enabled yes --appendonly yes --port 6380
72dbd4eef385a6dd521b8167619542b7b75d049dc306ef33c4478537f5ee8153
[root@localhost tomcatData]# docker run -d --name redis-node-3 --net host --privileged=true -v /redis/redis-node-3:/data redis --cluster-enabled yes --appendonly yes --port 6381
b385ca96ea0d29ad7d5dda0f1ab69d2d359e6009587d83500f2c586ef656b319
[root@localhost tomcatData]# docker run -d --name redis-node-4 --net host --privileged=true -v /redis/redis-node-4:/data redis --cluster-enabled yes --appendonly yes --port 6382
808b5e0c9ddb7736e0855644b917da05ad0ec307a4b1eb39b967ccb3edff1ed5
[root@localhost tomcatData]# docker run -d --name redis-node-5 --net host --privileged=true -v /redis/redis-node-5:/data redis --cluster-enabled yes --appendonly yes --port 6383
9a7156a41bc4abe6edb0f45354dc1aa1a812e2c8a667ea53036f66690317ba51
[root@localhost tomcatData]# docker run -d --name redis-node-6 --net host --privileged=true -v /redis/redis-node-6:/data redis --cluster-enabled yes --appendonly yes --port 6384
8016db0a503c2563fe06433d347191c84388d39f7d4cefec069e1e2bfe8ca07f

4、查看docker容器

[root@localhost tomcatData]# docker ps
CONTAINER ID   IMAGE     COMMAND                  CREATED              STATUS              PORTS     NAMES
8016db0a503c   redis     "docker-entrypoint.s…"   3 seconds ago        Up 3 seconds                  redis-node-6
9a7156a41bc4   redis     "docker-entrypoint.s…"   15 seconds ago       Up 14 seconds                 redis-node-5
808b5e0c9ddb   redis     "docker-entrypoint.s…"   27 seconds ago       Up 26 seconds                 redis-node-4
b385ca96ea0d   redis     "docker-entrypoint.s…"   40 seconds ago       Up 39 seconds                 redis-node-3
72dbd4eef385   redis     "docker-entrypoint.s…"   53 seconds ago       Up 53 seconds                 redis-node-2
7f597842ac76   redis     "docker-entrypoint.s…"   About a minute ago   Up About a minute             redis-node-1

5、进入节点1，构建6台节点的集群关系

命令格式： --cluster-replicas 1 表示为每个master创建一个slave节点

redis-cli --cluster create 192.168.109.141:6379 192.168.109.141:6380 192.168.109.141:6381 192.168.109.141:6382 192.168.109.141:6383 192.168.109.141:6384 --cluster-replicas 1

[root@localhost redis]# docker exec -it 7f597842ac76 /bin/bash
root@localhost:/data# redis-cli --cluster create 192.168.109.141:6379 192.168.109.141:6380 192.168.109.141:6381 192.168.109.141:6382 192.168.109.141:6383 192.168.109.141:6384 --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 192.168.109.141:6383 to 192.168.109.141:6379
Adding replica 192.168.109.141:6384 to 192.168.109.141:6380
Adding replica 192.168.109.141:6382 to 192.168.109.141:6381
>>> Trying to optimize slaves allocation for anti-affinity
[WARNING] Some slaves are in the same host as their master
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[0-5460] (5461 slots) master
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[5461-10922] (5462 slots) master
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[10923-16383] (5461 slots) master
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
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 192.168.109.141:6379)
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
root@localhost:/data#

6、查看主从关系

命令格式：redis-cli --cluster check 【本台redis自己的IP】:【本台redis自己的端口】

root@localhost:/data# redis-cli --cluster check 192.168.109.141:6379
192.168.109.141:6379 (ac91d148...) -> 0 keys | 5461 slots | 1 slaves.
192.168.109.141:6381 (1d822dd5...) -> 0 keys | 5461 slots | 1 slaves.
192.168.109.141:6380 (5ed4b671...) -> 0 keys | 5462 slots | 1 slaves.
[OK] 0 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.109.141:6379)
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

7、数据读写测试

加参数 -c ，防止路由失效

root@localhost:/data# redis-cli -p 6379
127.0.0.1:6379> get name
(error) MOVED 5798 192.168.109.141:6380
127.0.0.1:6379> set name zhangsan
(error) MOVED 5798 192.168.109.141:6380
127.0.0.1:6379>

root@localhost:/data# redis-cli -p 6379 -c
127.0.0.1:6379> get name
-> Redirected to slot [5798] located at 192.168.109.141:6380
"zhangsan"
192.168.109.141:6380>

8、从节点读数据测试：

情况：redis cluster集群中slave节点能成功复制master节点数据槽数据，但是无法get数据，显示只能到对应的master节点读取
原因：Redis Cluster集群中的从节点，官方默认设置的是不分担读请求的、只作备份和故障转移用,当有请求读向从节点时，会被重定向对应的主节点来处理
解决办法：在get数据之前先使用命令readonly,这个readonly告诉 Redis Cluster 从节点客户端愿意读取可能过时的数据并且对写请求不感兴趣
注意:断开连接后readonly就失效了，再次连接需要重新使用该命令

root@localhost:/data# redis-cli -p 6381
127.0.0.1:6381> get age
(error) MOVED 741 192.168.109.144:6385
127.0.0.1:6381> readonly
OK
127.0.0.1:6381> get age
"50"
127.0.0.1:6381>

二、容错切换迁移

1、情况——集群中某一台主机节点停机后再恢复

1）停节点node1主机

docker stop [容器ID]

2）查看集群状态(从机变主机)

cluster nodes

3）原主机恢复

docker start [容器ID]

4）查看集群状态（node1变从机）

cluster nodes

2、情况——主节点挂掉后再恢复，查看主备数据一致性

3、情况——集群中某一主从都挂掉，读写数据情况

三、主从扩容

1、创建两个容器开启集群模式

[root@localhost redis]# docker run -d --name redis-node-7 --net host --privileged=true -v /redis/redis-node-7:/data redis --cluster-enabled yes --appendonly yes --port 6385
3ee891534940154a539d38717475f4c358c4e48a80c9cef85ca14e4d5410c721
[root@localhost redis]# docker run -d --name redis-node-8 --net host --privileged=true -v /redis/redis-node-8:/data redis --cluster-enabled yes --appendonly yes --port 6386
0561fc04757e90da47c850d198e8eade0925c93099b1214468bf31783cd81c67
[root@localhost redis]# docker ps
CONTAINER ID   IMAGE     COMMAND                  CREATED          STATUS          PORTS     NAMES
0561fc04757e   redis     "docker-entrypoint.s…"   6 seconds ago    Up 2 seconds              redis-node-8
3ee891534940   redis     "docker-entrypoint.s…"   20 seconds ago   Up 19 seconds             redis-node-7
8016db0a503c   redis     "docker-entrypoint.s…"   42 minutes ago   Up 42 minutes             redis-node-6
9a7156a41bc4   redis     "docker-entrypoint.s…"   42 minutes ago   Up 42 minutes             redis-node-5
808b5e0c9ddb   redis     "docker-entrypoint.s…"   42 minutes ago   Up 42 minutes             redis-node-4
b385ca96ea0d   redis     "docker-entrypoint.s…"   42 minutes ago   Up 42 minutes             redis-node-3
72dbd4eef385   redis     "docker-entrypoint.s…"   42 minutes ago   Up 42 minutes             redis-node-2
7f597842ac76   redis     "docker-entrypoint.s…"   43 minutes ago   Up 43 minutes             redis-node-1
[root@localhost redis]#

2、进入node7容器，将node7作为主机加入集群

redis-cli --cluster add-node 自己实际IP地址:6387 自己实际IP地址:6381
6387 就是将要作为master新增节点
6381 就是原来集群节点里面的领路人，相当于6387拜拜6381的码头从而找到组织加入集群

[root@localhost redis]# docker exec -it 3ee891534940 /bin/bash
root@localhost:/data# redis-cli --cluster add-node 192.168.109.141:6385 192.168.109.141:6379
>>> Adding node 192.168.109.141:6385 to cluster 192.168.109.141:6379
>>> Performing Cluster Check (using node 192.168.109.141:6379)
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 192.168.109.141:6385 to make it join the cluster.
[OK] New node added correctly.

最后一行中 New node added correctly.表示新节点加入了集群

3、查看集群情况

新节点并没有分配到槽点

root@localhost:/data# redis-cli --cluster check 192.168.109.141:6385
192.168.109.141:6385 (d26431f5...) -> 0 keys | 0 slots | 0 slaves.
192.168.109.141:6381 (1d822dd5...) -> 0 keys | 5461 slots | 1 slaves.
192.168.109.141:6379 (ac91d148...) -> 0 keys | 5461 slots | 1 slaves.
192.168.109.141:6380 (5ed4b671...) -> 1 keys | 5462 slots | 1 slaves.
[OK] 1 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.109.141:6385)
M: d26431f565b881bcb84c4827d8496c51df7683bd 192.168.109.141:6385
   slots: (0 slots) master
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

4、分配槽号

重新分派槽号
命令:redis-cli --cluster reshard IP地址:端口号
redis-cli --cluster reshard 192.168.111.147:6381
redis-cli --cluster reshard 192.168.109.141:6379

root@localhost:/data# redis-cli --cluster reshard 192.168.109.141:6379
>>> Performing Cluster Check (using node 192.168.109.141:6379)
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
M: d26431f565b881bcb84c4827d8496c51df7683bd 192.168.109.141:6385
   slots: (0 slots) master
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

16384除以主节点数量=4096
How many slots do you want to move (from 1 to 16384)? 4096

How many slots do you want to move (from 1 to 16384)? 4096

新加入主节点的ID

What is the receiving node ID? d26431f565b881bcb84c4827d8496c51df7683bd

请输入所有原集群中主节点参与重新分配槽号的ID：
all表示所有
输入多个Id时以done结束

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: all

Ready to move 4096 slots.
  Source nodes:
    M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
       slots:[0-5460] (5461 slots) master
       1 additional replica(s)
    M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
       slots:[10923-16383] (5461 slots) master
       1 additional replica(s)
    M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
       slots:[5461-10922] (5462 slots) master
       1 additional replica(s)
  Destination node:
    M: d26431f565b881bcb84c4827d8496c51df7683bd 192.168.109.141:6385
       slots: (0 slots) master
  Resharding plan:
  Moving slot 5461 from 5ed4b6716402e263b10efeb19c86e91caeee7623
    Moving slot 5462 from 5ed4b6716402e263b10efeb19c86e91caeee7623
    Moving slot 5463 from 5ed4b6716402e263b10efeb19c86e91caeee7623
    Moving slot 5464 from 5ed4b6716402e263b10efeb19c86e91caeee7623
    Moving slot 5465 from 5ed4b6716402e263b10efeb19c86e91caeee7623
    Moving slot 5466 from 5ed4b6716402e263b10efeb19c86e91caeee7623
    Moving slot 5467 from 5ed4b6716402e263b10efeb19c86e91caeee7623
    Moving slot 5468 from 5ed4b6716402e263b10efeb19c86e91caeee7623

是否要继续执行提议的重新分片计划（是/否）？是的

Do you want to proceed with the proposed reshard plan (yes/no)? yes

5、检查集群状态

为什么6387是3个新的区间，以前的还是连续？
重新分配成本太高，所以前3家各自匀出来一部分，从6379/6380/6381三个旧节点分别匀出1364个坑位给新节点6385

root@localhost:/data# redis-cli --cluster check 192.168.109.141:6385
192.168.109.141:6385 (d26431f5...) -> 1 keys | 4096 slots | 0 slaves.
192.168.109.141:6381 (1d822dd5...) -> 0 keys | 4096 slots | 1 slaves.
192.168.109.141:6379 (ac91d148...) -> 0 keys | 4096 slots | 1 slaves.
192.168.109.141:6380 (5ed4b671...) -> 0 keys | 4096 slots | 1 slaves.
[OK] 1 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.109.141:6385)
M: d26431f565b881bcb84c4827d8496c51df7683bd 192.168.109.141:6385
   slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[1365-5460] (4096 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
root@localhost:/data#

6、为主节点分配从节点

命令：redis-cli --cluster add-node ip:新slave端口 ip:新master端口 --cluster-slave --cluster-master-id 新主机节点ID

redis-cli --cluster add-node 192.168.109.141:6386 192.168.109.141:6385 --cluster-slave --cluster-master-id d26431f565b881bcb84c4827d8496c51df7683bd

root@localhost:/data# redis-cli --cluster add-node 192.168.109.141:6386 192.168.109.141:6385 --cluster-slave --cluster-master-id d26431f565b881bcb84c4827d8496c51df7683bd
>>> Adding node 192.168.109.141:6386 to cluster 192.168.109.141:6385
>>> Performing Cluster Check (using node 192.168.109.141:6385)
M: d26431f565b881bcb84c4827d8496c51df7683bd 192.168.109.141:6385
   slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[1365-5460] (4096 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 192.168.109.141:6386 to make it join the cluster.
Waiting for the cluster to join

>>> Configure node as replica of 192.168.109.141:6385.
[OK] New node added correctly.

7、查看集群状态

redis-cli --cluster check 192.168.109.141:6385

root@localhost:/data# redis-cli --cluster check 192.168.109.141:6385
192.168.109.141:6385 (d26431f5...) -> 1 keys | 4096 slots | 1 slaves.
192.168.109.141:6381 (1d822dd5...) -> 0 keys | 4096 slots | 1 slaves.
192.168.109.141:6379 (ac91d148...) -> 0 keys | 4096 slots | 1 slaves.
192.168.109.141:6380 (5ed4b671...) -> 0 keys | 4096 slots | 1 slaves.
[OK] 1 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.109.141:6385)
M: d26431f565b881bcb84c4827d8496c51df7683bd 192.168.109.141:6385
   slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
   1 additional replica(s)
S: e1653a89863a31a8f60c0e7562e9297b8492e490 192.168.109.141:6386
   slots: (0 slots) slave
   replicates d26431f565b881bcb84c4827d8496c51df7683bd
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[1365-5460] (4096 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
root@localhost:/data#

四、主从缩容

1、查看集群状态

root@localhost:/data# redis-cli --cluster check 192.168.109.141:6385
192.168.109.141:6385 (d26431f5...) -> 1 keys | 4096 slots | 1 slaves.
192.168.109.141:6381 (1d822dd5...) -> 0 keys | 4096 slots | 1 slaves.
192.168.109.141:6379 (ac91d148...) -> 0 keys | 4096 slots | 1 slaves.
192.168.109.141:6380 (5ed4b671...) -> 0 keys | 4096 slots | 1 slaves.
[OK] 1 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.109.141:6385)
M: d26431f565b881bcb84c4827d8496c51df7683bd 192.168.109.141:6385
   slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
   1 additional replica(s)
S: e1653a89863a31a8f60c0e7562e9297b8492e490 192.168.109.141:6386
   slots: (0 slots) slave
   replicates d26431f565b881bcb84c4827d8496c51df7683bd
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[1365-5460] (4096 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
root@localhost:/data#

2、将6386从节点移除集群

命令：redis-cli --cluster del-node ip:从机端口 从机6386节点ID

 root@localhost:/data# redis-cli --cluster del-node 192.168.109.141:6386 e1653a89863a31a8f60c0e7562e9297b8492e490
>>> Removing node e1653a89863a31a8f60c0e7562e9297b8492e490 from cluster 192.168.109.141:6386
>>> Sending CLUSTER FORGET messages to the cluster...
>>> Sending CLUSTER RESET SOFT to the deleted node.
root@localhost:/data#

检查集群情况，发现6386已经没有了

root@localhost:/data# redis-cli --cluster check 192.168.109.141:6385
192.168.109.141:6385 (d26431f5...) -> 1 keys | 4096 slots | 0 slaves.
192.168.109.141:6381 (1d822dd5...) -> 0 keys | 4096 slots | 1 slaves.
192.168.109.141:6379 (ac91d148...) -> 0 keys | 4096 slots | 1 slaves.
192.168.109.141:6380 (5ed4b671...) -> 0 keys | 4096 slots | 1 slaves.
[OK] 1 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.109.141:6385)
M: d26431f565b881bcb84c4827d8496c51df7683bd 192.168.109.141:6385
   slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[1365-5460] (4096 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
root@localhost:/data#

3、将6385主节点的槽号移除，重新分配到其他主节点

1）移动2096个槽位到6379

root@localhost:/data# redis-cli --cluster reshard 192.168.109.141:6380
>>> Performing Cluster Check (using node 192.168.109.141:6380)
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
M: d26431f565b881bcb84c4827d8496c51df7683bd 192.168.109.141:6385
   slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[1365-5460] (4096 slots) master
   1 additional replica(s)
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
[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)? 2096

接收槽位的主节点ID，这里我用的6379节点在集群中的ID

What is the receiving node ID? ac91d14851cf4f35a376a453b452c06a9d065069

从哪个主节点移出槽位，这里我用6385节点在集群中的ID

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: d26431f565b881bcb84c4827d8496c51df7683bd
Source node #2: done

是否按照以上规划分配：是

    Moving slot 6189 from d26431f565b881bcb84c4827d8496c51df7683bd
    Moving slot 6190 from d26431f565b881bcb84c4827d8496c51df7683bd
    Moving slot 6191 from d26431f565b881bcb84c4827d8496c51df7683bd
Do you want to proceed with the proposed reshard plan (yes/no)? yes
Moving slot 0 from 192.168.109.141:6385 to 192.168.109.141:6379:
Moving slot 1 from 192.168.109.141:6385 to 192.168.109.141:6379:
Moving slot 2 from 192.168.109.141:6385 to 192.168.109.141:6379:

检查集群状态：
发现6379多个2096个槽位

root@localhost:/data# redis-cli --cluster check 192.168.109.141:6385
192.168.109.141:6385 (d26431f5...) -> 0 keys | 2000 slots | 0 slaves.
192.168.109.141:6381 (1d822dd5...) -> 0 keys | 4096 slots | 1 slaves.
192.168.109.141:6379 (ac91d148...) -> 1 keys | 6192 slots | 1 slaves.
192.168.109.141:6380 (5ed4b671...) -> 0 keys | 4096 slots | 1 slaves.
[OK] 1 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.109.141:6385)
M: d26431f565b881bcb84c4827d8496c51df7683bd 192.168.109.141:6385
   slots:[6192-6826],[10923-12287] (2000 slots) master
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[0-6191] (6192 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[6827-10922] (4096 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

2）移动2000个槽位到6380

同上

4、检查集群情况

6385节点已经没有槽位了

root@localhost:/data# redis-cli --cluster check 192.168.109.141:6385
192.168.109.141:6385 (d26431f5...) -> 0 keys | 0 slots | 0 slaves.
192.168.109.141:6381 (1d822dd5...) -> 0 keys | 4096 slots | 1 slaves.
192.168.109.141:6379 (ac91d148...) -> 1 keys | 6192 slots | 1 slaves.
192.168.109.141:6380 (5ed4b671...) -> 0 keys | 6096 slots | 1 slaves.
[OK] 1 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.109.141:6385)
M: d26431f565b881bcb84c4827d8496c51df7683bd 192.168.109.141:6385
   slots: (0 slots) master
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[0-6191] (6192 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[6192-12287] (6096 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
root@localhost:/data#

5、将6385主节点移除集群

命令：redis-cli --cluster del-node 6385的ip:端口 6385节点ID

root@localhost:/data# redis-cli --cluster del-node 192.168.109.141:6385 d26431f565b881bcb84c4827d8496c51df7683bd
>>> Removing node d26431f565b881bcb84c4827d8496c51df7683bd from cluster 192.168.109.141:6385
>>> Sending CLUSTER FORGET messages to the cluster...
>>> Sending CLUSTER RESET SOFT to the deleted node.

6、查看集群状态

root@localhost:/data# redis-cli --cluster check 192.168.109.141:6381
192.168.109.141:6381 (1d822dd5...) -> 0 keys | 4096 slots | 1 slaves.
192.168.109.141:6379 (ac91d148...) -> 1 keys | 6192 slots | 1 slaves.
192.168.109.141:6380 (5ed4b671...) -> 0 keys | 6096 slots | 1 slaves.
[OK] 1 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.109.141:6381)
M: 1d822dd5b1886b84b6697543471f5916cdaa3665 192.168.109.141:6381
   slots:[12288-16383] (4096 slots) master
   1 additional replica(s)
S: 933b378ec43d9d016997ff93f16a812723657d15 192.168.109.141:6382
   slots: (0 slots) slave
   replicates ac91d14851cf4f35a376a453b452c06a9d065069
M: ac91d14851cf4f35a376a453b452c06a9d065069 192.168.109.141:6379
   slots:[0-6191] (6192 slots) master
   1 additional replica(s)
S: d43e6129151a03404212826cb48d20eb591c4d8a 192.168.109.141:6383
   slots: (0 slots) slave
   replicates 5ed4b6716402e263b10efeb19c86e91caeee7623
M: 5ed4b6716402e263b10efeb19c86e91caeee7623 192.168.109.141:6380
   slots:[6192-12287] (6096 slots) master
   1 additional replica(s)
S: 98318770a6f56c9a9b3f00b4797d367ea955cc09 192.168.109.141:6384
   slots: (0 slots) slave
   replicates 1d822dd5b1886b84b6697543471f5916cdaa3665
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
邱秋Elena
关注
  • 3
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Redis的常用命令&集群节点管理
黎明强的博客
08-04 3542
返回有序集key中，所有score值介于min和max之间（包含等于min或max）的成员。有序集成员按score值递增（从小到大）次序排列，最小的是最上面。移除有序集 key 中，指定排名(rank)区间内的所有成员。操作多字节位域 （获取当前月的所有签到数据 ， 计算连续签到天数）获取集合的值并按照score排序 ( 最小的是最上面)根据value获取某个值的位置 【获取排序号，默认小到大】查询指定字节区间的第一个被设置成1的bit位的位置。根据key中的某个value值 ，返回score。...
redis集群模式
qq_44189274的博客
08-01 248
redis的三种模式: 1.主从复制模式 2.哨兵模式 3.集群化模式
总结Redis Cluster原理+基本使用+运维注意事项_redis cluster 使用(1)
最新发布
2401_83621634的博客
05-07 775
在分布式存储中需要提供维护节点元数据信息的机制，所谓元数据是指：节点负责哪些数据，是否出现故障等状态信息。常见的元数据维护方式分为：集中式和P2P方式。Redis集群采用P2P的Gossip（流言）协议，Gossip协议工作原理就是节点彼此不断通信交换信息，一段时间后所有的节点都会知道集群完整的信息，这种方式类似流言传播。
Docker Swarm 集群
KingCruel的专栏
12-03 764
docker swarm 集群
docker redis集群配置
西卡卡的博客
06-14 661
docker下redis集群配置，集群读写，主从扩容，主从缩容
Redis集群介绍
黑木爷的专栏
11-06 476
能够对外提供相同服务的多台服务器组成的集合。
Docker Redis 集群安装
01-07
docker pull redis:5.0.3 增加配置文件redis-cluster.tmpl 在用户目录下创建文件 ${userpath}/redis-cluster/redis-cluster.tmpl port ${PORT} protected-mode no cluster-enabled yes cluster-config-file nodes....
Docker redis 集群搭建
01-20
Docker redis 集群搭建 Redis 集群是一个提供在多个 Redis 节点间共享数据的程序集。 Redis 集群并不支持处理多个 keys 的命令,因为这需要在不同的节点间移动数据，从而达不到像 Redis 那样的性能，在高负载的情况...
一键shell脚本搭建docker redis 集群（cluster）
12-30
为了新手小伙伴发愁集群... "`docker network ls | grep redis | awk '{print $1}'`"] && docker network create redis --subnet 172.18.0.0/16 --gateway 172.18.0.1 #查看网卡信息 docker network ls | grep redis
docker-compose一键搭建Redis集群
06-12
1.先运行 createFile.py 输入宿主机IP地址，输入redis密码 2.按照控制台输出执行docker-compose up -d 启动命令 3.启动成功后执行加入集群命令即可
docker redis 3.2 配置文件
03-21
在这个场景中，我们有一个针对 Redis 3.2 版本的自定义配置文件 `redis.conf`，该文件是为在 Docker 环境下调试 Redis 实例而设计的。下面将详细解释配置文件中的关键设置和它们在 Docker 容器中的作用。 1. **端口...
Redis-cluster 命令查看服务情况
难得糊涂
08-26 1万+
序言 目前没发现什么比较好的可视化的Redis服务监控.如果你有什么好的开源redis开源监控请推荐给我.~~~~cuiyaonan2000@163.com 其实可以用该命令看,或者自己封装,因为很多其它的开源监控也是靠这些命令获取的信息.并且也没法深化去监控,如果要深化去监控只能加日志,比如在RedisUtil中的方法中进行拦截添加日志. 操作 如下-p 指定端口 -h指定ip....
Redis集群启动问题
m0_67265464的博客
03-23 2381
Redis集群启动问题 1、问题描述 2、问题分析 3、问题解决 4、总结 1、问题描述 [ERR] Node 192.168.43.175:7001 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0. 2、问题分析 这是由于redis集群在关闭的时候是非正常关闭，也就是俗称的宕机。redis服务器没来得及保存相关数据
查看redis集群状态_Redis集群原理的核心内容
weixin_39980841的博客
12-08 2104
架构师(JiaGouX)我们都是架构师！架构未来，你来不来？作者：古霜卡比原文：www.cnblogs.com/skabyy/p/10013322.html这几天工作需要研究了一下Redis集群，将其原理的核心内容记录下来以便以后查阅。集群原理一个系统建立集群主要需要解决两个问题：数据同步问题和集群容错问题。Naive方案一个简单粗暴的方案是部署多台一模一样的Redis服务，再用负载均...
redis集群模式运维常用命令及相关说明
无聊小刚的博客
12-13 5939
进入集群客户端 任意选一个redis节点，进入redis 所在目录 cd /redis 所在目录/bin/ ./redis-cli -h 本地节点的ip -p redis的端口号 -a 密码 查看集群中各个节点状态 进入到redis客户端后，运行如下命令，查看集群中节点状态 cluster nodes 会得到如下输出 模糊的部分为ip
A4-2-Linux下 Redis 集群使用（二）
谦怀
02-25 291
A4-2-Linux下 Redis 集群使用（二） 集群操作 一、查看集群信息 cluster info 查看集群状态，槽分配，集群大小等 cluster nodes 也可查看主从节点。 ./redis-cli --cluster check 10.0.0.12:20003 检查 二、新增节点 1、新增主节点 创建新实例 cd /usr/local/redis-clu...
Redis高可用集群-哨兵模式（Redis-Sentinel）搭建配置教程【Windows环境】
ToBeMaybe_的博客
03-19 538
Redis哨兵模式，用现在流行的话可以说就是一个“哨兵机器人”，给“哨兵机器人”进行相应的配置之后，这个"机器人"可以7*24小时工作，它能能够自动帮助你做一些事情，如监控，提醒，自动处理故障等。 Redis-sentinel简介 Redis-sentinel是Redis的作者antirez，因为Redis集群的被各大公司使用，每个公司要写自己的集群管理工具，于是antirez花了几个星期写出了R...
redis cluster管理工具redis-trib.rb详解
热门推荐
胡杰的专栏
03-24 6万+
redis cluster管理工具redis-trib.rb详解 redis-trib.rb 命令 command 详解
REDIS学习（6）查看redis状态，以及rdb和aof两种持久化方案的区别
kkgbn的博客
09-07 6779
在控制台输入info命令回车可以得到以下的信息（也可以用 redis clients分别查找信息） redis_version:3.2.3服务器版本 redis_git_sha1:00000000 redis_git_dirty:0 redis_build_id:78f5751fe6f1a0f3 redis_mode:standalone os:Linux 2.6.32-431.23.
docker redis集群
03-02
Docker Redis集群是一种使用Docker容器技术来部署和管理Redis集群的方法。Redis是一个开源的内存数据存储系统，常用于缓存、消息队列和数据存储等场景。通过使用Docker容器，可以方便地创建、启动和管理多个Redis...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值