快速部署Redis集群---看了就懂

快速部署Redis集群

一、Redis集群简介

Redis Cluster是一个无中心的结构，每个节点都保存数据和整个群集的状态。每个节点都会保存其他节点的信息，知道其他节点所负责的槽，并且会与其他节点定时发送心跳信息，能够及时感知群集中异常的节点。
Redis没有统一的路口，当客户端向群集中任一节点发送与数据库键有关的命令时，接受命令的节点会计算出命令要处理的数据库键属于哪个槽，并检查这个槽是否指派给了自己。如果键所在的槽正好指派给了当前节点，那么节点直接执行这个命令；如果键所在的槽并没有指派给当前节点，那么节点会向客户端返回一个MOVED错误，指引客户端转向（redirect）正确的节点，并再次发送之前想要执行的命令。

二、搭建Redis集群

1、案例环境

master1：20.0.0.10
master2：20.0.0.11
master3：20.0.0.12
slave1： 20.0.0.13
slave2 ： 20.0.0.14
slave3： 20.0.0.16

2、实验步骤

2.1 六台服务器都先编译安装redis

[root@master1 ~] yum -y install gcc gcc-c++ make
[root@master1 ~] tar zxf redis-5.0.7.tar.gz
[root@master1 ~] cd redis-5.0.7/
[root@master1 redis-5.0.7] make
[root@master1 redis-5.0.7] make PREFIX=/usr/local/redis install

2.2、修改配置文件（六台都要）

[root@Master1 ~] vi /etc/redis/6379.conf
 70 bind 192.168.73.10  ###删除之前的127.0.0.1，改为各主机的IP地址
 89 protected-mode no  ###关闭保护模式
 137 daemonize yes  ###以独立进程启动
 833 cluster-enabled yes  ###开启群集功能
 841 cluster-config-file nodes-6379.conf  ###群集名称文件设置
 847 cluster-node-timeout 15000  ###群集超时时间
 700 appendonly yes  ###开启aof持久化

2.3、正常启动后，/var/lib/redis/6379/目录下会多出三个文件，第一个是持久化文件appendonly.aof，第二个是RDB持久文件dump.rdb，另外一个是节点首次启动生成的nodes-6379.conf

[root@master2 ~] cd /var/lib/redis/6379/
[root@master2 6379]# ll
总用量 8
-rw-r--r--. 1 root root   0 11月 12 16:34 appendonly.aof
-rw-r--r--. 1 root root  92 11月 12 16:34 dump.rdb
-rw-r--r--. 1 root root 114 11月 12 16:34 nodes-6379.conf

2.4、导入redis-3.2.0.gem 至/OPT并执行，仅在一台redis中操作，准备生成集群

[root@master1 ~] yum -y install ruby rubygems
[root@master1 ~] gem install redis-3.2.0.gem 
Successfully installed redis-3.2.0
Parsing documentation for redis-3.2.0
Installing ri documentation for redis-3.2.0
1 gem installed

2.5、创建集群

六个实例分为三组，每组一主一从，–replicas 1表示每组一个从，下面交互的时候需要输入yes才可以创建。

[root@master1 ~] redis-cli --cluster create --cluster-replicas 1 20.0.0.10:6379 20.0.0.11:6379 20.0.0.12:6379 20.0.0.13:6379 20.0.0.14:6379 20.0.0.16:6379
>>> Performing hash slots allocation on 6 nodes...
Master[0] -> Slots 0 - 5460
Master[1] -> Slots 5461 - 10922
Master[2] -> Slots 10923 - 16383       ###哈希槽
Adding replica 20.0.0.14:6379 to 20.0.0.10:6379
Adding replica 20.0.0.16:6379 to 20.0.0.11:6379
Adding replica 20.0.0.13:6379 to 20.0.0.12:6379       ###主从对应关系
M: 32b17a36e7cb751ce768630de6cdaa3a1d51b0f4 20.0.0.10:6379
   slots:[0-5460] (5461 slots) master
M: 7f2b0c73b5bf9bbda7578081fa345eb81acf6772 20.0.0.11:6379
   slots:[5461-10922] (5462 slots) master
M: 4b6e380bfc2e56e0be3af504f3278a4f76cb10fc 20.0.0.12:6379
   slots:[10923-16383] (5461 slots) master
S: 638aa6d6f802c42fd727c347806c6433af8aa77b 20.0.0.13:6379
   replicates 4b6e380bfc2e56e0be3af504f3278a4f76cb10fc
S: f1513baf2b2cf262c5bea7ab0ef9bff1a899ba29 20.0.0.14:6379
   replicates 32b17a36e7cb751ce768630de6cdaa3a1d51b0f4
S: 3fcdf8d25e36a665e09ec70763c419772d8104e4 20.0.0.16:6379
   replicates 7f2b0c73b5bf9bbda7578081fa345eb81acf6772
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 20.0.0.10:6379)
M: 32b17a36e7cb751ce768630de6cdaa3a1d51b0f4 20.0.0.10:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: 7f2b0c73b5bf9bbda7578081fa345eb81acf6772 20.0.0.11:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: f1513baf2b2cf262c5bea7ab0ef9bff1a899ba29 20.0.0.14:6379
   slots: (0 slots) slave
   replicates 32b17a36e7cb751ce768630de6cdaa3a1d51b0f4
M: 4b6e380bfc2e56e0be3af504f3278a4f76cb10fc 20.0.0.12:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
S: 3fcdf8d25e36a665e09ec70763c419772d8104e4 20.0.0.16:6379
   slots: (0 slots) slave
   replicates 7f2b0c73b5bf9bbda7578081fa345eb81acf6772
S: 638aa6d6f802c42fd727c347806c6433af8aa77b 20.0.0.13:6379
   slots: (0 slots) slave
   replicates 4b6e380bfc2e56e0be3af504f3278a4f76cb10fc
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

2.6、主从数据库验证

[root@master1 ~]# redis-cli -h 20.0.0.11 -p 6379 -c
20.0.0.11:6379> set score 100
-> Redirected to slot [5176] located at 20.0.0.10:6379
OK
20.0.0.10:6379> exit
[root@master1 ~]# redis-cli -h 20.0.0.12 -p 6379 -c
20.0.0.12:6379> get score
-> Redirected to slot [5176] located at 20.0.0.10:6379
"100"

查看群集状态
[root@master1 ~]# redis-cli -h 20.0.0.10 -p 6379 
20.0.0.10: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:491
cluster_stats_messages_pong_sent:532
cluster_stats_messages_sent:1023
cluster_stats_messages_ping_received:527
cluster_stats_messages_pong_received:491
cluster_stats_messages_meet_received:5
cluster_stats_messages_received:1023

查看节点信息
20.0.0.10:6379> cluster nodes
7f2b0c73b5bf9bbda7578081fa345eb81acf6772 20.0.0.11:6379@16379 master - 0 1605172303515 2 connected 5461-10922
f1513baf2b2cf262c5bea7ab0ef9bff1a899ba29 20.0.0.14:6379@16379 slave 32b17a36e7cb751ce768630de6cdaa3a1d51b0f4 0 1605172305531 5 connected
32b17a36e7cb751ce768630de6cdaa3a1d51b0f4 20.0.0.10:6379@16379 myself,master - 0 1605172301000 1 connected 0-5460
4b6e380bfc2e56e0be3af504f3278a4f76cb10fc 20.0.0.12:6379@16379 master - 0 1605172303000 3 connected 10923-16383
3fcdf8d25e36a665e09ec70763c419772d8104e4 20.0.0.16:6379@16379 slave 7f2b0c73b5bf9bbda7578081fa345eb81acf6772 0 1605172301000 6 connected
638aa6d6f802c42fd727c347806c6433af8aa77b 20.0.0.13:6379@16379 slave 4b6e380bfc2e56e0be3af504f3278a4f76cb10fc 0 1605172304525 4 connected