Redis主从集群搭建三主三从集群在Linux环境下配置-----Redis

旧约Alatus

已于 2024-02-23 21:40:59 修改

阅读量852

点赞数 24

分类专栏： # Redis 数据库文章标签： mybatis 后端 redis nosql nosql数据库 database 缓存

于 2024-02-23 15:53:45 首次发布

本文链接：https://blog.csdn.net/2201_75960169/article/details/136258030

版权

数据库同时被 2 个专栏收录

106 篇文章 0 订阅

订阅专栏

Redis

79 篇文章 0 订阅

订阅专栏

redis-cli -a abc123 --cluster create --cluster-replicas 1 192.168.127.128:6381 192.168.127.128:6382 192.168.127.130:6383 192.168.127.130:6384 192.168.127.129:6385 192.168.127.129:6386
redis-cli -a abc123 --cluster create --cluster-replicas 1 192.168.127.128:6381 192.168.127.128:6382 192.168.127.130:6383 192.168.127.130:6384 192.168.127.129:6385 192.168.127.129:6386

>>> 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.127.130:6384 to 192.168.127.128:6381
Adding replica 192.168.127.129:6386 to 192.168.127.130:6383
Adding replica 192.168.127.128:6382 to 192.168.127.129:6385
M: 1d9d15d019c1cf5093ecdaf472ca2f7d00eb00de 192.168.127.128:6381
   slots:[0-5460] (5461 slots) master
S: 76da20d313ba2c18ad7a8f5aea43477cb8d2a471 192.168.127.128:6382
   replicates e1247a24f7e0dfcf10707965bac7f1b76f1b2224
M: 791a71de88aff2e1b3e7e50cdcc8bc1b93a0810b 192.168.127.130:6383
   slots:[5461-10922] (5462 slots) master
S: 9f8a054e4d11a7a4268989c858321b80b57ee1d5 192.168.127.130:6384
   replicates 1d9d15d019c1cf5093ecdaf472ca2f7d00eb00de
M: e1247a24f7e0dfcf10707965bac7f1b76f1b2224 192.168.127.129:6385
   slots:[10923-16383] (5461 slots) master
S: 2eb9983fd5e30501e9b97f17d501f8d00d573417 192.168.127.129:6386
   replicates 791a71de88aff2e1b3e7e50cdcc8bc1b93a0810b
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.127.128:6381)
M: 1d9d15d019c1cf5093ecdaf472ca2f7d00eb00de 192.168.127.128:6381
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 76da20d313ba2c18ad7a8f5aea43477cb8d2a471 192.168.127.128:6382
   slots: (0 slots) slave
   replicates e1247a24f7e0dfcf10707965bac7f1b76f1b2224
S: 9f8a054e4d11a7a4268989c858321b80b57ee1d5 192.168.127.130:6384
   slots: (0 slots) slave
   replicates 1d9d15d019c1cf5093ecdaf472ca2f7d00eb00de
S: 2eb9983fd5e30501e9b97f17d501f8d00d573417 192.168.127.129:6386
   slots: (0 slots) slave
   replicates 791a71de88aff2e1b3e7e50cdcc8bc1b93a0810b
M: e1247a24f7e0dfcf10707965bac7f1b76f1b2224 192.168.127.129:6385
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
M: 791a71de88aff2e1b3e7e50cdcc8bc1b93a0810b 192.168.127.130:6383
   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.
>>> 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.127.130:6384 to 192.168.127.128:6381
Adding replica 192.168.127.129:6386 to 192.168.127.130:6383
Adding replica 192.168.127.128:6382 to 192.168.127.129:6385
M: 1d9d15d019c1cf5093ecdaf472ca2f7d00eb00de 192.168.127.128:6381
slots:[0-5460] (5461 slots) master
S: 76da20d313ba2c18ad7a8f5aea43477cb8d2a471 192.168.127.128:6382
replicates e1247a24f7e0dfcf10707965bac7f1b76f1b2224
M: 791a71de88aff2e1b3e7e50cdcc8bc1b93a0810b 192.168.127.130:6383
slots:[5461-10922] (5462 slots) master
S: 9f8a054e4d11a7a4268989c858321b80b57ee1d5 192.168.127.130:6384
replicates 1d9d15d019c1cf5093ecdaf472ca2f7d00eb00de
M: e1247a24f7e0dfcf10707965bac7f1b76f1b2224 192.168.127.129:6385
slots:[10923-16383] (5461 slots) master
S: 2eb9983fd5e30501e9b97f17d501f8d00d573417 192.168.127.129:6386
replicates 791a71de88aff2e1b3e7e50cdcc8bc1b93a0810b
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.127.128:6381)
M: 1d9d15d019c1cf5093ecdaf472ca2f7d00eb00de 192.168.127.128:6381
slots:[0-5460] (5461 slots) master
1 additional replica(s)
S: 76da20d313ba2c18ad7a8f5aea43477cb8d2a471 192.168.127.128:6382
slots: (0 slots) slave
replicates e1247a24f7e0dfcf10707965bac7f1b76f1b2224
S: 9f8a054e4d11a7a4268989c858321b80b57ee1d5 192.168.127.130:6384
slots: (0 slots) slave
replicates 1d9d15d019c1cf5093ecdaf472ca2f7d00eb00de
S: 2eb9983fd5e30501e9b97f17d501f8d00d573417 192.168.127.129:6386
slots: (0 slots) slave
replicates 791a71de88aff2e1b3e7e50cdcc8bc1b93a0810b
M: e1247a24f7e0dfcf10707965bac7f1b76f1b2224 192.168.127.129:6385
slots:[10923-16383] (5461 slots) master
1 additional replica(s)
M: 791a71de88aff2e1b3e7e50cdcc8bc1b93a0810b 192.168.127.130:6383
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.

bind 0.0.0.0
daemonize yes
protected-mode no
port 6383
logfile "/myredis/cluster/cluster6383.log"
pidfile /myredis/cluster6383.pid
dir /myredis/cluster
dbfilename dump6383.rdb
appendonly yes
appendfilename "appendonly6383.aof"
requirepass abc123
masterauth abc123
 
 
cluster-enabled yes
cluster-config-file nodes-6383.conf
cluster-node-timeout 5000
bind 0.0.0.0
daemonize yes
protected-mode no
port 6383
logfile "/myredis/cluster/cluster6383.log"
pidfile /myredis/cluster6383.pid
dir /myredis/cluster
dbfilename dump6383.rdb
appendonly yes
appendfilename "appendonly6383.aof"
requirepass abc123
masterauth abc123

cluster-enabled yes
cluster-config-file nodes-6383.conf
cluster-node-timeout 5000