Redis集群中的节点操作

最新推荐文章于 2022-07-13 11:43:28 发布
最新推荐文章于 2022-07-13 11:43:28 发布
阅读量577 收藏
点赞数 1
CC 4.0 BY-SA版权
分类专栏： Redis
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/suchenbin/article/details/97641776

添加节点

1）、启动添加的节点，新增7007、7008节点

[root@*** cluster]# mkdir 7007
[root@*** cluster]# cp 7001/redis7001.conf  7007/redis7007.conf
[root@*** cluster]# vim 7007/redis7007.conf 
[root@*** cluster]# mkdir 7008
[root@*** cluster]# cp 7001/redis7001.conf  7008/redis7008.conf
[root@*** cluster]# vim 7008/redis7008.conf 
[root@*** cluster]# ./redis-5.0.4/src/redis-server  7007/redis7007.conf  &
[1] 10823
[root@*** cluster]# ./redis-5.0.4/src/redis-server  7008/redis7008.conf  &
[2] 10829
[1]   Done                    ./redis-5.0.4/src/redis-server 7007/redis7007.conf
[root@*** cluster]# ps -ef|grep redis
root     10595     1  0 14:23 ?        00:00:00 ./redis-5.0.4/src/redis-server 0.0.0.0:7001 [cluster]
root     10824     1  0 14:39 ?        00:00:00 ./redis-5.0.4/src/redis-server 0.0.0.0:7007 [cluster]
root     10830     1  0 14:39 ?        00:00:00 ./redis-5.0.4/src/redis-server 0.0.0.0:7008 [cluster]
root     10835  6959  0 14:39 pts/1    00:00:00 grep --color=auto redis
root     31219     1  0 Jul28 ?        00:00:41 ./redis-5.0.4/src/redis-server 0.0.0.0:7002 [cluster]
root     31224     1  0 Jul28 ?        00:00:43 ./redis-5.0.4/src/redis-server 0.0.0.0:7003 [cluster]
root     31229     1  0 Jul28 ?        00:00:43 ./redis-5.0.4/src/redis-server 0.0.0.0:7004 [cluster]
root     31234     1  0 Jul28 ?        00:00:46 ./redis-5.0.4/src/redis-server 0.0.0.0:7005 [cluster]
root     31240     1  0 Jul28 ?        00:00:42 ./redis-5.0.4/src/redis-server 0.0.0.0:7006 [cluster]
[2]+  Done                    ./redis-5.0.4/src/redis-server 7008/redis7008.conf

2）、查看节点信息

[root@*** cluster]# ./redis-5.0.4/src/redis-cli -c -p 7001
127.0.0.1:7001> cluster nodes
85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004@17004 slave e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 0 1564382535278 8 connected
17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006@17006 slave d2a31afbd940004162e94c681cff06862a5af72c 0 1564382533000 11 connected
e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003@17003 master - 0 1564382535000 8 connected 5462-10922
da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002@17002 master - 0 1564382532274 12 connected 0-5461
d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005@17005 master - 0 1564382536280 11 connected 10923-16383
38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001@17001 myself,slave da006b8e1615f7d338d25bedfb7899eab79e42d2 0 1564382534000 10 connected

 3）、添加主节点信息

将7007节点加入到集群中：./redis-cli --cluster add-node  节点 集群任一节点

[root@*** cluster]# ./redis-5.0.4/src/redis-cli --cluster add-node 192.168.0.111:7007 192.168.0.111:7001
>>> Adding node 192.168.0.111:7007 to cluster 192.168.0.111:7001
>>> Performing Cluster Check (using node 192.168.0.111:7001)
S: 38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001
   slots: (0 slots) slave
   replicates da006b8e1615f7d338d25bedfb7899eab79e42d2
S: 85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004
   slots: (0 slots) slave
   replicates e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3
S: 17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006
   slots: (0 slots) slave
   replicates d2a31afbd940004162e94c681cff06862a5af72c
M: e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003
   slots:[5462-10922] (5461 slots) master
   1 additional replica(s)
M: da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002
   slots:[0-5461] (5462 slots) master
   1 additional replica(s)
M: d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005
   slots:[10923-16383] (5461 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.
>>> Send CLUSTER MEET to node 192.168.0.111:7007 to make it join the cluster.
[OK] New node added correctly.
[root@*** cluster]# ./redis-5.0.4/src/redis-cli -c -p 7001
127.0.0.1:7001> cluster nodes
85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004@17004 slave e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 0 1564383120000 8 connected
17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006@17006 slave d2a31afbd940004162e94c681cff06862a5af72c 0 1564383115158 11 connected
e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003@17003 master - 0 1564383121168 8 connected 5462-10922
3cad6291c3a949409be29c49c528d95de10ef692 192.168.0.111:7007@17007 master - 0 1564383118000 0 connected
da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002@17002 master - 0 1564383119000 12 connected 0-5461
d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005@17005 master - 0 1564383120167 11 connected 10923-16383
38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001@17001 myself,slave da006b8e1615f7d338d25bedfb7899eab79e42d2 0 1564383118000 10 connected

给7007分配槽，reshard命令

127.0.0.1:7001> quit
[root@*** cluster]# ./redis-5.0.4/src/redis-cli --cluster reshard 192.168.0.111:7001
>>> Performing Cluster Check (using node 192.168.0.111:7001)
S: 38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001
   slots: (0 slots) slave
   replicates da006b8e1615f7d338d25bedfb7899eab79e42d2
S: 85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004
   slots: (0 slots) slave
   replicates e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3
S: 17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006
   slots: (0 slots) slave
   replicates d2a31afbd940004162e94c681cff06862a5af72c
M: e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003
   slots:[6128-10922] (4795 slots) master
   1 additional replica(s)
M: 3cad6291c3a949409be29c49c528d95de10ef692 192.168.0.111:7007
   slots:[0-666],[5462-6127],[10923-11588] (1999 slots) master
M: da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002
   slots:[667-5461] (4795 slots) master
   1 additional replica(s)
M: d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005
   slots:[11589-16383] (4795 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)? 2000
What is the receiving node ID? 3cad6291c3a949409be29c49c528d95de10ef692
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
.
.
.

Do you want to proceed with the proposed reshard plan (yes/no)? yes
.
.
.
Moving slot 11586 from 192.168.0.111:7005 to 192.168.0.111:7007: 
Moving slot 11587 from 192.168.0.111:7005 to 192.168.0.111:7007: 
Moving slot 11588 from 192.168.0.111:7005 to 192.168.0.111:7007:

 查看槽分配情况

[root@*** cluster]# ./redis-5.0.4/src/redis-cli -c -p 7001
127.0.0.1:7001> cluster nodes
85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004@17004 slave e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 0 1564383859000 8 connected
17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006@17006 slave d2a31afbd940004162e94c681cff06862a5af72c 0 1564383860278 11 connected
e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003@17003 master - 0 1564383859000 8 connected 6128-10922
3cad6291c3a949409be29c49c528d95de10ef692 192.168.0.111:7007@17007 master - 0 1564383861279 13 connected 0-666 5462-6127 10923-11588
da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002@17002 master - 0 1564383859277 12 connected 667-5461
d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005@17005 master - 0 1564383857275 11 connected 11589-16383
38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001@17001 myself,slave da006b8e1615f7d338d25bedfb7899eab79e42d2 0 1564383860000 10 connected

 4）、添加从节点

将节点7008添加到集群中

127.0.0.1:7001>  quit
[root@*** cluster]# ./redis-5.0.4/src/redis-cli --cluster add-node 192.168.0.111:7008 192.168.0.111:7001
>>> Adding node 192.168.0.111:7008 to cluster 192.168.0.111:7001
>>> Performing Cluster Check (using node 192.168.0.111:7001)
S: 38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001
   slots: (0 slots) slave
   replicates da006b8e1615f7d338d25bedfb7899eab79e42d2
S: 85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004
   slots: (0 slots) slave
   replicates e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3
S: 17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006
   slots: (0 slots) slave
   replicates d2a31afbd940004162e94c681cff06862a5af72c
M: e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003
   slots:[6128-10922] (4795 slots) master
   1 additional replica(s)
M: 3cad6291c3a949409be29c49c528d95de10ef692 192.168.0.111:7007
   slots:[0-666],[5462-6127],[10923-11588] (1999 slots) master
M: da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002
   slots:[667-5461] (4795 slots) master
   1 additional replica(s)
M: d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005
   slots:[11589-16383] (4795 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.
>>> Send CLUSTER MEET to node 192.168.0.111:7008 to make it join the cluster.
[OK] New node added correctly.

 查看节点信息

[root@*** cluster]# ./redis-5.0.4/src/redis-cli -c -p 7001
127.0.0.1:7001> cluster nodes
85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004@17004 slave e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 0 1564388890000 8 connected
46b8f36c720f76a1c3d6e6a8bff1426a996760fa 192.168.0.111:7008@17008 master - 0 1564388887000 0 connected
17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006@17006 slave d2a31afbd940004162e94c681cff06862a5af72c 0 1564388888000 11 connected
e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003@17003 master - 0 1564388890000 8 connected 6128-10922
3cad6291c3a949409be29c49c528d95de10ef692 192.168.0.111:7007@17007 master - 0 1564388891000 13 connected 0-666 5462-6127 10923-11588
da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002@17002 master - 0 1564388890000 12 connected 667-5461
d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005@17005 master - 0 1564388891932 11 connected 11589-16383
38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001@17001 myself,slave da006b8e1615f7d338d25bedfb7899eab79e42d2 0 1564388888000 10 connected

将7008设置成7007的从节点，切换到从节点（7008）下，执行cluster replicate 主节点id

127.0.0.1:7001> quit
[root@*** cluster]# ./redis-5.0.4/src/redis-cli -c -p 7008
127.0.0.1:7008> cluster replicate 3cad6291c3a949409be29c49c528d95de10ef692
OK
127.0.0.1:7008> cluster nodes
d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005@17005 master - 0 1564390547748 11 connected 11589-16383
38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001@17001 slave da006b8e1615f7d338d25bedfb7899eab79e42d2 0 1564390546000 12 connected
17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006@17006 slave d2a31afbd940004162e94c681cff06862a5af72c 0 1564390546000 11 connected
46b8f36c720f76a1c3d6e6a8bff1426a996760fa 192.168.0.111:7008@17008 myself,slave 3cad6291c3a949409be29c49c528d95de10ef692 0 1564390548000 0 connected
85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004@17004 slave e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 0 1564390547000 8 connected
da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002@17002 master - 0 1564390547000 12 connected 667-5461
3cad6291c3a949409be29c49c528d95de10ef692 192.168.0.111:7007@17007 master - 0 1564390548750 13 connected 0-666 5462-6127 10923-11588
e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003@17003 master - 0 1564390544000 8 connected 6128-10922

删除节点

删除从节点（7008），查看节点信息

./redis-cli --cluster del-node 从节点ip:port 从节点id

127.0.0.1:7008> quit
[root@*** cluster]# ./redis-5.0.4/src/redis-cli --cluster del-node 192.168.0.111:7008 46b8f36c720f76a1c3d6e6a8bff1426a996760fa
>>> Removing node 46b8f36c720f76a1c3d6e6a8bff1426a996760fa from cluster 192.168.0.111:7008
>>> Sending CLUSTER FORGET messages to the cluster...
>>> SHUTDOWN the node.
[root@*** cluster]# ./redis-5.0.4/src/redis-cli -c -p 7001
127.0.0.1:7001> cluster nodes
85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004@17004 slave e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 0 1564390952064 8 connected
17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006@17006 slave d2a31afbd940004162e94c681cff06862a5af72c 0 1564390951062 11 connected
e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003@17003 master - 0 1564390950000 8 connected 6128-10922
3cad6291c3a949409be29c49c528d95de10ef692 192.168.0.111:7007@17007 master - 0 1564390950000 13 connected 0-666 5462-6127 10923-11588
da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002@17002 master - 0 1564390950061 12 connected 667-5461
d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005@17005 master - 0 1564390949060 11 connected 11589-16383
38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001@17001 myself,slave da006b8e1615f7d338d25bedfb7899eab79e42d2 0 1564390949000 10 connected

删除主节点（7007）

主节点（7007）中存在槽，在删除主节点之前需要迁移到其他主节点（7002）

127.0.0.1:7001> quit
[root@*** cluster]# ./redis-5.0.4/src/redis-cli --cluster reshard 192.168.0.111:7001
>>> Performing Cluster Check (using node 192.168.0.111:7001)
S: 38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001
   slots: (0 slots) slave
   replicates da006b8e1615f7d338d25bedfb7899eab79e42d2
S: 85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004
   slots: (0 slots) slave
   replicates e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3
S: 17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006
   slots: (0 slots) slave
   replicates d2a31afbd940004162e94c681cff06862a5af72c
M: e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003
   slots:[6128-10922] (4795 slots) master
   1 additional replica(s)
M: 3cad6291c3a949409be29c49c528d95de10ef692 192.168.0.111:7007
   slots:[0-666],[5462-6127],[10923-11588] (1999 slots) master
M: da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002
   slots:[667-5461] (4795 slots) master
   1 additional replica(s)
M: d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005
   slots:[11589-16383] (4795 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)? 2000
What is the receiving node ID? da006b8e1615f7d338d25bedfb7899eab79e42d2
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: 3cad6291c3a949409be29c49c528d95de10ef692
Source node #2: done
.
.
.
    Moving slot 11587 from 3cad6291c3a949409be29c49c528d95de10ef692
    Moving slot 11588 from 3cad6291c3a949409be29c49c528d95de10ef692
Do you want to proceed with the proposed reshard plan (yes/no)? yes
.
.
.
Moving slot 11586 from 192.168.0.111:7007 to 192.168.0.111:7002: 
Moving slot 11587 from 192.168.0.111:7007 to 192.168.0.111:7002: 
Moving slot 11588 from 192.168.0.111:7007 to 192.168.0.111:7002:

查看节点信息，7007下的槽已经迁移到7002

[root@***cluster]# ./redis-5.0.4/src/redis-cli -c -p 7001
127.0.0.1:7001> cluster nodes
85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004@17004 slave d2a31afbd940004162e94c681cff06862a5af72c 0 1564393685241 15 connected
17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006@17006 slave da006b8e1615f7d338d25bedfb7899eab79e42d2 0 1564393686000 19 connected
e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003@17003 master - 0 1564393686000 17 connected 6128-10922
3cad6291c3a949409be29c49c528d95de10ef692 192.168.0.111:7007@17007 master - 0 1564393686243 18 connected
da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002@17002 master - 0 1564393687244 19 connected 0-6127 10923-11588
d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005@17005 master - 0 1564393685000 15 connected 11589-16383
38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001@17001 myself,slave e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 0 1564393685000 10 connected

删除节点7007，再次查看节点信息

127.0.0.1:7001> quit
You have new mail in /var/spool/mail/root
[root@*** cluster]# ./redis-5.0.4/src/redis-cli --cluster del-node 192.168.0.111:7007 3cad6291c3a949409be29c49c528d95de10ef692
>>> Removing node 3cad6291c3a949409be29c49c528d95de10ef692 from cluster 192.168.0.111:7007
>>> Sending CLUSTER FORGET messages to the cluster...
>>> SHUTDOWN the node.
[root@*** cluster]# ./redis-5.0.4/src/redis-cli -c -p 7001
127.0.0.1:7001> cluster nodes
85d9276e71faf2a3bfe7c9041d920678c4082623 192.168.0.111:7004@17004 slave d2a31afbd940004162e94c681cff06862a5af72c 0 1564393885000 15 connected
17c67f03e8354f492fbd4a6be1f79a53c23e8507 192.168.0.111:7006@17006 slave da006b8e1615f7d338d25bedfb7899eab79e42d2 0 1564393884537 19 connected
e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 192.168.0.111:7003@17003 master - 0 1564393884000 17 connected 6128-10922
da006b8e1615f7d338d25bedfb7899eab79e42d2 192.168.0.111:7002@17002 master - 0 1564393885538 19 connected 0-6127 10923-11588
d2a31afbd940004162e94c681cff06862a5af72c 192.168.0.111:7005@17005 master - 0 1564393886539 15 connected 11589-16383
38206edb37cf100e20085da0affaeced4ae42029 192.168.0.111:7001@17001 myself,slave e4fee6a90d5b071ad514cd30f8d5d9a1c13947b3 0 1564393885000 10 connected

 

 

如果有写的不对的地方，请大家多多批评指正，非常感谢！

【Redis】Redis 集群中节点之间如何通信？
杰叔叔不是个好叔叔的博客
01-16 1066
Redis集群中节点间通信是指Redis集群中的各个节点通过一定的协议和机制相互传递信息，以实现集群的协调、数据同步、故障检测等功能。在分布式系统中，不同的节点进行数据/信息共享是一个基本的需求。一种比较简单粗暴的方法就是集中式发散消息，简单来说就是一个主节点同时共享最新信息给其他所有节点，比较适合中心化系统。这种方法的缺陷也很明显，节点多的时候不光同步消息的效率低，还太依赖与中心节点，存在单点风险问题。1、相比于其他分布式协议/算法来说，Gossip 协议理解起来非常简单。
redis集群节点宕机 fail状态 redis的投票机制实测
01-07
本文测试 redis集群节点宕机 fail状态以上篇博文为基础Redis集群策略及集群实例。  在Redis集群策略及集群实例中通过单机集群创建多实例（3主3从）的方式搭建了redis集群，以此为基础做实测  首先查看一下集群状态...
Redis-Cluster操作详解
feinifi的博客
11-28 998
redis集群操作详解
（八）Redis集群常用命令、集群节点新增删除
OceanSky的专栏
01-14 1万+
参考文章：http://doc.redisfans.com/topic/cluster-tutorial.html 一、cluster info :打印集群信息 二、cluster nodes:列出集群中已知的所有节点（node）,以及这些节点相关 信息 可以看到上面有六个节点，三个主节点（master），三个备份节点（slave），其中有一个端口为7001的主节点前有myself节点代...
Redis集群常见操作
u012333307的专栏
03-07 1454
常见设置设置最大内存maxmemory 2548000000如果不需要持久化时，去掉持久化功能注释掉save行启动时作用守护进程daemonize yes集群配置port 7000 cluster-enabled yes cluster-config-file nodes.conf cluster-node-timeout 5000 appendonly yes常见命令查看集群状态redis/src
Not all slots covered! Only 10922 slots are available
xiaohanstu的专栏
07-13 1万+
Caused by: org.redisson.client.RedisConnectionException: Not all slots covered! Only 10922 slots are available. Set checkSlotsCoverage = false to avoid this check.
redis cluster 搭建
天堂无语
06-29 1223
redis cluster搭建，初学者遇到的一些问题及解决办法
Redis集群数据迁移操作文档
06-29
实际迁移过程中，我们以两个场景为例：一是从一个Redis集群（Cluster_A）迁移到另一个Redis集群（Cluster_B），二是从Redis集群（Cluster_A）迁移到单个Redis实例（Redis_C）。在迁移前，务必先检查源和目标Redis...
Redis Cluster集群部署-故障模拟-监控
品尝人生百态
01-08 843
一.基础环境 1):准备系统:Centos7.x Ansible 2):准备主机: 192.168.1.115 redis01 192.168.1.192 redis02 192.168.1.23 redis03 192.168.1.47 redis04 192.168.1.65 redis05 192.168.1.14 redis06 3):软件存放目录:/applica...
redis cluster管理工具redis-trib.rb详解
热门推荐
胡杰的专栏
03-24 6万+
redis cluster管理工具redis-trib.rb详解 redis-trib.rb 命令 command 详解
redis集群安装配置
北风之神
09-01 962
redis.conf port 7001 daemonize yes cluster-enabled yes cluster-config-file nodes.conf cluster-node-timeout 5000 appendonly yes bind 192.168.4.70 [root@redis1 src]# ./redis-
Redis 集群
xiao-fei的博客
11-02 257
搭建Redis 集群的过程： 集群介绍： redis3.x 后的集群 ，是多主多从的集群，多个主机组成一个集群的主体，共同负责对外提供读写服务。 每个主机都有自己的从机，从机的主要工作是：1. 同步主机数据 2.当主机宕机时顶替主机。 搭建过程（在linux系统模拟） 一、安装依赖 安装流程： 1、yum -y inst...
分布式缓存技术redis学习系列（四）——redis高级应用（集群搭建、集群分区原理、集群操作）
javaloveiphone的专栏
08-29 7769
本文我们继续学习redis的高级特性——集群。本文主要内容包括集群搭建、集群分区原理和集群操作的学习。Redis集群简介Redis 集群是3.0之后才引入的，在3.0之前，使用哨兵（sentinel）机制（本文将不做介绍，大家可另行查阅）来监控各个节点之间的状态。Redis 集群可谓是让很多人久等了。Redis 集群是一组能进行数据共享的Redis 实例（服务或者节点）的设施，集群可以使用的功能是普
Redis集群cluster：增加删除（伸缩）节点操作步骤
qq_17732903的博客
06-28 4425
Redis集群cluster：增加删除（伸缩）节点操作步骤。 因为是自己练习的，所有没有弄多台服务器来练习。
关于redis集群方案
劝君与我同风起，扶摇直上九万里
03-25 3701
最近在研究redis集群方案，看到知乎上有个朋友写的观点很好，就先收过来了。原文见：http://www.zhihu.com/question/21419897
redis 集群中 Slave-read-only 参数的使用注意事项
raoping2017的博客
05-11 2万+
文章目录1、概述 2、redis 集群中 Slave-read-only 参数的使用注意事项 3、操作示例 4、小结 1、概述介绍 redis 集群参数使用技巧。 2、redis 集群中 Slave-read-only 参数的使用注意事项如果为yes，代表为只读状态，但并不表示客户端用集群方式以从节点为入口连入集群时，不可以进行set操作，且set操作的数据不会被放在从节点的槽上，会被放到某主节点的
Redis(设计与实现):49---集群之集群节点、节点启动（CLUSTER MEET/NODE命令、cluster-enabled选项）
董哥的黑板报
12-02 1137
一、集群介绍 Redis集群是Redis提供的分布式数据库方案，集群通过分片（sharding）来进行数据共享，并提供复制和故障转移功能 二、集群节点介绍 一个Redis集群通常由多个节点（node）组成，在刚开始的时候，每个节点都是相互独立的，它们都处于一个只包含自己的集群当中，要组建一个真正可工作的集群，我们必须将各个独立的节点连接起来，构成一个包含多个节点的集群 节点的连接（CLUST...
redis--节点新增，切换，数据迁移
wuxu_nanjing的博客
09-13 3531
新增redis节点， redis版本为redis-3.0.7   ruby-2.2.2 添加主节点到集群命令：  [xxxxxx src]# ./redis-trib.rb  add-node 192.168.76.116:6380 192.168.76.116:6379 >>> Adding node 192.168.76.116:6380 to cluster 192.1
redis集群新增节点操作
最新发布
06-15
Redis 集群是通过 Redis 的哨兵（Sentinel）或自动分片（Cluster Mode）来实现的高可用性和扩展性的解决方案。在集群中添加新节点通常涉及以下步骤： 1. **计划和准备**： - 确保你有足够资源的新节点，并且已经配置好 Redis 服务器。 - 了解新节点的网络位置，以便它能与现有集群中的节点正常通信。 2. **加入集群**： - 对于 Sentinel 集群模式，你需要在 Sentinel 中添加新节点。首先，配置 Sentinel 认识新节点，然后使用 `sentinel add-slave` 命令指定主节点和新节点，设置相应的参数如权重、端口等。 - 对于 Cluster 模式，直接启动新节点，配置为集群节点。在启动时，新节点会自动发现并加入到集群中，通过交互式命令行或配置文件配置 `cluster add-node`。 3. **数据同步**： - 新加入的节点会自动从其他节点同步数据。这可能是一个耗时的过程，取决于集群的大小和数据量。 - 如果是首次加入，可能需要手动进行部分或全量的数据复制。 4. **节点角色确认**： - 在数据同步完成后，新节点的角色（master, slave, 或者 replica）可能需要被 Sentinel 或者集群本身确认。 5. **监控和测试**： - 使用 `CLUSTER NODES` 和 `INFO CLUSTER` 等命令检查节点状态和连接情况。 - 测试新节点的性能和功能，确保它能正常参与到集群服务中。 **相关问题**: 1. 哨兵模式和自动分片模式有什么区别？ 2. 如何通过 Sentinel 配置新的 Sentinel 节点？ 3. 新节点如何识别并加入到 Cluster 模式中的其他节点？ 4. 在哪些情况下需要手动干预数据同步过程？
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值