Redis5.0 Cluster集群搭建及扩容-低调大师

Redis5.0 Cluster集群搭建及扩容

2020-12-09 586

Redis3.0之后，Redis官方提供了完整的集群解决方案。该方案采用去中心化的方式，包括：sharding（分区）、replication（复制）、failover（故障转移），称为RedisCluster。Redis5.0前采用redis-trib进行集群的创建和管理，需要ruby支持。Redis5.0可以直接使用Redis-cli进行集群的创建和管理。这里主要介绍使用Redis5.0.10搭建RedisCluster集群

1.环境准备

1.1 集群规划

Maste1 - 192.168.1.161:6379 
Slave1 - 192.168.1.161:6380
Maste2 - 192.168.1.162:6379
Slave2 - 192.168.1.162:6380
Maste3 - 192.168.1.163:6379
Slave3 - 192.168.1.163:6380
Maste4(扩容) - 192.168.1.165:6379
Slave4(扩容) - 192.168.1.165:6380

Redis集群最少需要6个节点，可以分布在一台或者多台主机上。本次使用4台虚拟机，先161,162,163上搭建一个三主三从的集群，每台虚拟机上安装6379和6380两个节点。集群搭建成功后，在165上新建两个节点（一主一从），将两个新的节点加入集群，来验证集群扩容。

1.2 安装包下载准备

wget https://download.redis.io/releases/redis-5.0.10.tar.gz
tar -zxvf redis-5.0.10.tar.gz
cd redis-5.0.10
mkdir -p /opt/redis-cluster/6379 /opt/redis-cluster/6380
make install PREFIX=/opt/redis-cluster/6379
make install PREFIX=/opt/redis-cluster/6380
cp redis.conf  /opt/redis-cluster/6379/bin
cp redis.conf  /opt/redis-cluster/6380/bin

2.集群配置

2.1 修改每台服务器上的节点配置文件

修改/opt/redis-cluster/6379/bin/redis.conf

###1.注释掉bind
#bind 127.0.0.1
###2.修改protected-mode为no
protected-mode no
###3.修改cluster-enable为 yes
cluster-enable yes
###4.修改daemonize为 yes
daemonize yes

修改/opt/redis-cluster/6380/bin/redis.conf

###1.注释掉bind
#bind 127.0.0.1
###2.修改protected-mode为no
protected-mode no
###3.修改cluster-enable为 yes
cluster-enable yes
###4.修改daemonize为 yes
daemonize yes
###5.port 修改为6380
port 6380
###6.修改pidfile 为 /var/run/redis_6380.pid
pidfile /var/run/redis_6380.pid

2.2 启动节点

cd /opt/redis-cluster/6379/bin/
./redis-server redis.conf
cd /opt/redis-cluster/6380/bin/
./redis-server redis.conf
##查看节点是否启动
 ps -ef|grep redis

2.3 创建Redis集群

选取一个节点执行创建集群命令，如下：

[root@master bin]# cd /opt/redis-cluster/6379/bin/
[root@master bin]# ./redis-cli --cluster create 192.168.1.161:6379 192.168.1.162:6379 192.168.1.163:6379 192.168.1.161:6380 192.168.1.162:6380 192.168.1.163:6380 --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.1.162:6380 to 192.168.1.161:6379
Adding replica 192.168.1.163:6380 to 192.168.1.162:6379
Adding replica 192.168.1.161:6380 to 192.168.1.163:6379
M: 64364a4b2de9a82653b46be040e86f600fb5ac2d 192.168.1.161:6379
   slots:[0-5460] (5461 slots) master
M: 9ee1767e39b07033b480c82337620ed006162c8a 192.168.1.162:6379
   slots:[5461-10922] (5462 slots) master
M: 041fcc81090840f67efed70d3cd623076d15dbc4 192.168.1.163:6379
   slots:[10923-16383] (5461 slots) master
S: f59d4108d4fbe145c2d9c6f2d70e06991a4d63be 192.168.1.161:6380
   replicates 041fcc81090840f67efed70d3cd623076d15dbc4
S: 113134e4cedc9069db1af667b2f6cf23097d0b3e 192.168.1.162:6380
   replicates 64364a4b2de9a82653b46be040e86f600fb5ac2d
S: 65ad86c316f6452ca6a7429febe4a9d96f6c2e43 192.168.1.163:6380
   replicates 9ee1767e39b07033b480c82337620ed006162c8a
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.1.161:6379)
M: 64364a4b2de9a82653b46be040e86f600fb5ac2d 192.168.1.161:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 113134e4cedc9069db1af667b2f6cf23097d0b3e 192.168.1.162:6380
   slots: (0 slots) slave
   replicates 64364a4b2de9a82653b46be040e86f600fb5ac2d
M: 041fcc81090840f67efed70d3cd623076d15dbc4 192.168.1.163:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
M: 9ee1767e39b07033b480c82337620ed006162c8a 192.168.1.162:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: 65ad86c316f6452ca6a7429febe4a9d96f6c2e43 192.168.1.163:6380
   slots: (0 slots) slave
   replicates 9ee1767e39b07033b480c82337620ed006162c8a
S: f59d4108d4fbe145c2d9c6f2d70e06991a4d63be 192.168.1.161:6380
   slots: (0 slots) slave
   replicates 041fcc81090840f67efed70d3cd623076d15dbc4
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@master bin]#

如上，集群创建成功。可以通过redis-cli连接查看集群状态：

./redis-cli -h 127.0.0.1 -p 6379 -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:168
cluster_stats_messages_pong_sent:164
cluster_stats_messages_sent:332
cluster_stats_messages_ping_received:159
cluster_stats_messages_pong_received:168
cluster_stats_messages_meet_received:5
cluster_stats_messages_received:332
###查看进群节点
127.0.0.1:6379> cluster nodes
113134e4cedc9069db1af667b2f6cf23097d0b3e 192.168.1.162:6380@16380 slave 64364a4b2de9a82653b46be040e86f600fb5ac2d 0 1604321562000 5 connected
041fcc81090840f67efed70d3cd623076d15dbc4 192.168.1.163:6379@16379 master - 0 1604321563496 3 connected 10923-16383
64364a4b2de9a82653b46be040e86f600fb5ac2d 192.168.1.161:6379@16379 myself,master - 0 1604321563000 1 connected 0-5460
9ee1767e39b07033b480c82337620ed006162c8a 192.168.1.162:6379@16379 master - 0 1604321562000 2 connected 5461-10922
65ad86c316f6452ca6a7429febe4a9d96f6c2e43 192.168.1.163:6380@16380 slave 9ee1767e39b07033b480c82337620ed006162c8a 0 1604321564506 6 connected
f59d4108d4fbe145c2d9c6f2d70e06991a4d63be 192.168.1.161:6380@16380 slave 041fcc81090840f67efed70d3cd623076d15dbc4 0 1604321562484 4 connected

3.集群扩容

3.1 添加新节点

[root@master bin]# cd /opt/redis-cluster/6379/bin/
[root@master bin]# ./redis-cli --cluster add-node 192.168.1.165:6379 192.168.1.161:6379
>>> Adding node 192.168.1.165:6379 to cluster 192.168.1.161:6379
>>> Performing Cluster Check (using node 192.168.1.161:6379)
M: 64364a4b2de9a82653b46be040e86f600fb5ac2d 192.168.1.161:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
S: 113134e4cedc9069db1af667b2f6cf23097d0b3e 192.168.1.162:6380
   slots: (0 slots) slave
   replicates 64364a4b2de9a82653b46be040e86f600fb5ac2d
M: 041fcc81090840f67efed70d3cd623076d15dbc4 192.168.1.163:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
M: 9ee1767e39b07033b480c82337620ed006162c8a 192.168.1.162:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: 65ad86c316f6452ca6a7429febe4a9d96f6c2e43 192.168.1.163:6380
   slots: (0 slots) slave
   replicates 9ee1767e39b07033b480c82337620ed006162c8a
S: f59d4108d4fbe145c2d9c6f2d70e06991a4d63be 192.168.1.161:6380
   slots: (0 slots) slave
   replicates 041fcc81090840f67efed70d3cd623076d15dbc4
[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.1.165:6379 to make it join the cluster.
[OK] New node added correctly.

此时查看节点状态：

[root@master bin]# ./redis-cli -h 127.0.0.1 -p 6379 -c
127.0.0.1:6379> cluster nodes
113134e4cedc9069db1af667b2f6cf23097d0b3e 192.168.1.162:6380@16380 slave 64364a4b2de9a82653b46be040e86f600fb5ac2d 0 1604321847825 5 connected
041fcc81090840f67efed70d3cd623076d15dbc4 192.168.1.163:6379@16379 master - 0 1604321842740 3 connected 10923-16383
64364a4b2de9a82653b46be040e86f600fb5ac2d 192.168.1.161:6379@16379 myself,master - 0 1604321844000 1 connected 0-5460
9ee1767e39b07033b480c82337620ed006162c8a 192.168.1.162:6379@16379 master - 0 1604321846808 2 connected 5461-10922
828c48dc72d52ff5be972512d3d87b70236af87c 192.168.1.165:6379@16379 master - 0 1604321845792 0 connected
65ad86c316f6452ca6a7429febe4a9d96f6c2e43 192.168.1.163:6380@16380 slave 9ee1767e39b07033b480c82337620ed006162c8a 0 1604321847000 6 connected
f59d4108d4fbe145c2d9c6f2d70e06991a4d63be 192.168.1.161:6380@16380 slave 041fcc81090840f67efed70d3cd623076d15dbc4 0 1604321844779 4 connected
127.0.0.1:6379>

看到165的6379节点已经存在，

3.2 新节点hash槽分配

需要给新节点进行hash槽分配，这样该主节才可以存储数据

连接上集群（连接集群中任意一个可用结点都行）

[root@master bin]# ./redis-cli --cluster reshard 192.168.1.165:6379
>>> Performing Cluster Check (using node 192.168.1.165:6379)
M: 828c48dc72d52ff5be972512d3d87b70236af87c 192.168.1.165:6379
   slots: (0 slots) master
M: 9ee1767e39b07033b480c82337620ed006162c8a 192.168.1.162:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
M: 64364a4b2de9a82653b46be040e86f600fb5ac2d 192.168.1.161:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: 041fcc81090840f67efed70d3cd623076d15dbc4 192.168.1.163:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
S: 65ad86c316f6452ca6a7429febe4a9d96f6c2e43 192.168.1.163:6380
   slots: (0 slots) slave
   replicates 9ee1767e39b07033b480c82337620ed006162c8a
S: 113134e4cedc9069db1af667b2f6cf23097d0b3e 192.168.1.162:6380
   slots: (0 slots) slave
   replicates 64364a4b2de9a82653b46be040e86f600fb5ac2d
S: f59d4108d4fbe145c2d9c6f2d70e06991a4d63be 192.168.1.161:6380
   slots: (0 slots) slave
   replicates 041fcc81090840f67efed70d3cd623076d15dbc4
[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)?

输入要分配的槽数量

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

输入接收槽的结点id

通过cluster nodes 查看新增的192.168.1.165:6379 的id为828c48dc72d52ff5be972512d3d87b70236af87c

What is the receiving node ID? 828c48dc72d52ff5be972512d3d87b70236af87c
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.

输入 all

然后输入输入yes确认

此时再通过cluster nodes查看节点，可以看到新节点分配的槽为0-1332 5461-6794 10923-12255

127.0.0.1:6379> cluster nodes
113134e4cedc9069db1af667b2f6cf23097d0b3e 192.168.1.162:6380@16380 slave 64364a4b2de9a82653b46be040e86f600fb5ac2d 0 1604322686164 5 connected
041fcc81090840f67efed70d3cd623076d15dbc4 192.168.1.163:6379@16379 master - 0 1604322684000 3 connected 12256-16383
64364a4b2de9a82653b46be040e86f600fb5ac2d 192.168.1.161:6379@16379 myself,master - 0 1604322684000 1 connected 1333-5460
9ee1767e39b07033b480c82337620ed006162c8a 192.168.1.162:6379@16379 master - 0 1604322685155 2 connected 6795-10922
828c48dc72d52ff5be972512d3d87b70236af87c 192.168.1.165:6379@16379 master - 0 1604322686000 7 connected 0-1332 5461-6794 10923-12255
65ad86c316f6452ca6a7429febe4a9d96f6c2e43 192.168.1.163:6380@16380 slave 9ee1767e39b07033b480c82337620ed006162c8a 0 1604322683000 6 connected
f59d4108d4fbe145c2d9c6f2d70e06991a4d63be 192.168.1.161:6380@16380 slave 041fcc81090840f67efed70d3cd623076d15dbc4 0 1604322685000 4 connected
127.0.0.1:6379>

3.3 给新节点添加从节点

给192.168.1.165:6379增加从节点192.168.1.165:6380

[root@master bin]# ./redis-cli --cluster add-node 192.168.1.165:6380 192.168.1.165:6379 --cluster-slave --cluster-master-id 828c48dc72d52ff5be972512d3d87b70236af87c
>>> Adding node 192.168.1.165:6380 to cluster 192.168.1.165:6379
>>> Performing Cluster Check (using node 192.168.1.165:6379)
M: 828c48dc72d52ff5be972512d3d87b70236af87c 192.168.1.165:6379
   slots:[0-1332],[5461-6794],[10923-12255] (4000 slots) master
M: 9ee1767e39b07033b480c82337620ed006162c8a 192.168.1.162:6379
   slots:[6795-10922] (4128 slots) master
   1 additional replica(s)
M: 64364a4b2de9a82653b46be040e86f600fb5ac2d 192.168.1.161:6379
   slots:[1333-5460] (4128 slots) master
   1 additional replica(s)
M: 041fcc81090840f67efed70d3cd623076d15dbc4 192.168.1.163:6379
   slots:[12256-16383] (4128 slots) master
   1 additional replica(s)
S: 65ad86c316f6452ca6a7429febe4a9d96f6c2e43 192.168.1.163:6380
   slots: (0 slots) slave
   replicates 9ee1767e39b07033b480c82337620ed006162c8a
S: 113134e4cedc9069db1af667b2f6cf23097d0b3e 192.168.1.162:6380
   slots: (0 slots) slave
   replicates 64364a4b2de9a82653b46be040e86f600fb5ac2d
S: f59d4108d4fbe145c2d9c6f2d70e06991a4d63be 192.168.1.161:6380
   slots: (0 slots) slave
   replicates 041fcc81090840f67efed70d3cd623076d15dbc4
[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.1.165:6380 to make it join the cluster.
Waiting for the cluster to join

>>> Configure node as replica of 192.168.1.165:6379.
[OK] New node added correctly.
[root@master bin]#

微信关注我们

原文链接：https://my.oschina.net/xingyuyu/blog/4783295

转载内容版权归作者及来源网站所有！

低调大师中文资讯倾力打造互联网数据资讯、行业资源、电子商务、移动互联网、网络营销平台。持续更新报道IT业界、互联网、市场资讯、驱动更新,是最及时权威的产业资讯及硬件资讯报道平台。

面试官本想拿一道求素数搞我，但被我优雅的"回击"了

点击上方蓝字关注我前言现在的面试官，是无数开发者的梦魇，能够吊打面试官的属实不多，因为大部分面试官真的有那么那几下子。但在面试中，我们这些小生存者不能全盘否定只能单点突破—从某个问题上让面试官眼前一亮。这不，今天就来分享来了。这年头，算法岗内卷不说，开发岗也有点内卷，对开发者要求越来越高了，而面试官也是处心积虑的 "刁难" 面试者，凡是都喜欢由浅入深，凡是都喜欢问个：你知道为什么？你知道原理吗？之类。并且，以前只是大厂面试官喜欢问算法，大厂员工底子好，很多甚至有ACM经验或者系统刷题经验，这很容易理解，但现在一些小公司面试官也是张口闭口 xx算法、xx数据结构你说说看，这不，真的被问到了。求一个质数在这么一次的过程，面试官问我算法题我不吃惊，我实现早把十大排序原理、复杂度分析、代码手写实现出来了，也把链表、树的各种操作温习的滚瓜烂熟，不过突然就是很诧异的面试官来了一道求素数问题，我把场景还原一下：面试官：你知道怎么求素数吗？我：求素数？面试官：是的，就是求素数。我：这很简单啊，判断一个数为素数，那么肯定就没有两个数(除了自身和1)相乘等于它，只需要枚举看看有没有能够被...

2020-12-08

537

为了提高前端开发效率, 笔者先后写了上百个前端工具, 有些是给公司内部使用的, 有些单纯是因为自己太“ 懒”, 不想写代码, 所以才“ 被迫”做的. 接下来介绍的一款工具—— css三角形生成器也是因为之前想要解放设计师的生产力, 自己又懒得切图或者写 css代码, 所以想来想去还是自己做一个能自动生成css三角形代码的工具吧. 接下来笔者就来带大家介绍一下这个工具的用途和实现方案, 方便大家后续可以扩展出更多的“ 懒人工具”. 在线css三角形生成器预览由预览动画我们可以看到通过在线工具我们可以轻松配置各种想要的三角形, 并且能实时查看 css代码. 开发完这个工具之后笔者再也不用担心还需要手写三角形代码了. (上班摸鱼也成了可能, 确实很多时候就是不想写代码还想要有钱拿) 在文末笔者会附上 css工具的在线地址, 接下来我们来看看具体实现流程. 实现css三角形生成器因为这个工具的需求来自于前端, 所以肯定是要对 css和 js编程有一定的基础, 比如css3的 transform, transition, 布局, 盒模型, border边界特性等. 和笔者之前写的任何一个...

2020-12-09

521

资源下载

更多资源

优质分享App

近一个月的开发和优化，本站点的第一个app全新上线。该app采用极致压缩，本体才4.36MB。系统里面做了大量数据访问、缓存优化。方便用户在手机上查看文章。后续会推出HarmonyOS的适配版本。

腾讯云软件源

为解决软件依赖安装时官方源访问速度慢的问题，腾讯云为一些软件搭建了缓存服务。您可以通过使用腾讯云软件源站来提升依赖包的安装速度。为了方便用户自由搭建服务架构，目前腾讯云软件源站支持公网访问和内网访问。

Nacos

Nacos /nɑ:kəʊs/ 是 Dynamic Naming and Configuration Service 的首字母简称，一个易于构建 AI Agent 应用的动态服务发现、配置管理和AI智能体管理平台。Nacos 致力于帮助您发现、配置和管理微服务及AI智能体应用。Nacos 提供了一组简单易用的特性集，帮助您快速实现动态服务发现、服务配置、服务元数据、流量管理。Nacos 帮助您更敏捷和容易地构建、交付和管理微服务平台。

Sublime Text

Sublime Text具有漂亮的用户界面和强大的功能，例如代码缩略图，Python的插件，代码段等。还可自定义键绑定，菜单和工具栏。Sublime Text 的主要功能包括：拼写检查，书签，完整的 Python API ， Goto 功能，即时项目切换，多选择，多窗口等等。Sublime Text 是一个跨平台的编辑器，同时支持Windows、Linux、Mac OS X等操作系统。