============ Redis 集群 ============
1、前置依赖:
1.1)、集群用到ruby命令,因此安装ruby,方式一
(1)、【yum install ruby】
(2)、【yum install rubygems】
(3)、【gem install redis】,安装redis和ruby接口,redis版本要2.2.x以上
1.2)、集群用到ruby命令,因此安装ruby,方式二
(1)、安装rvm
1]、切换到root目录下:【cd /】
2]、【gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB】
3]、【curl -sSL https://get.rvm.io | bash -s stable】
4]、【source /etc/profile.d/rvm.sh】
5]、查看是否安装成功:【rvm -v】
(2)、安装ruby:【rvm install 2.4.2】
(3)、【gem install redis】,安装redis和ruby接口,redis版本要2.2.x以上
2、说明:至少6台,3主3从,本例中【7001[master1]、7002[master2]、7003[master3]、7004[slave1]、7005[slave2]、7006[slave3]】,搭建在同台机器上
3、搭建步骤:
1)、分别在6台机器上递归创建文件夹:【mkdir -p /usr/local/redis-cluster/700*】
2)、将redis.conf配置文件分别copy到700*下,进行修改各个文件的内容
(1)、后台启动:【daemonize yes】
(2)、端口号:【port 700*】
(3)、绑定当前机器IP:【bind 192.168.56.101】
(4)、指定数据文件存放路径:【dir /usr/local/redis-cluster/700*/】,不修改担心丢失数据
(5)、持久方式开启快照:【appendonly yes】,生产上用【appendfsync always】
(6)、启动集群模式:【cluster-enabled yes】
(7)、节点配置文件与端口号对应:【cluster-config-file nodes700*.conf】,让每个节点相互知道对方的存在
(8)、设置超时时间:【cluster-node-timeout 15000】
4)、逐个启动6个redis实例:【/usr/local/redis/bin/redis-server /usr/local/redis-cluster/700*/redis.conf】
5)、检查是否启动成功:【ps -ef | grep redis】,查看是否已存在对应进程
6)、在redis的安装目录下,执行集群脚本:【/usr/local/redis-3.0.7/src/redis-trib.rb create --replicas 1 192.168.56.101:7001 192.168.56.102:7002 192.168.56.103:7003 192.168.56.104:7004 192.168.56.105:7005 192.168.56.106:7006】,下次重启机器不需要此操作
注:其中的 1 为主节点与从节点的比值(1 = 主节点数量/从节点数量),主节点排完,接着排从节点,一一对应,例如,7001为master1,则7004为slave1
7)、连接任意客户端:【/usr/local/redis/bin/redis-cli -c -h 192.168.56.101 -p 7001】(./redis-cli -c -h -p),[-c 表示集群模式,-h指定ip,-p指定端口号]
8)、验证集群是否搭建成功:查看集群信息【cluster info】,查看集群节点【cluster nodes】
9)、关闭集群:【/usr/local/redis/bin/redis-cli -c -h 192.168.56.101 -p 700* shutdown】,需要逐个关闭
注意:出现集群无法启动时,删除临时的数据文件,再次重新启动每个redis服务,然后重新构建集群环境
=======================成功出现的信息 start============================
[root@localhost ~]# /usr/local/redis-3.0.7/src/redis-trib.rb create --replicas 1 192.168.56.101:7001 192.168.56.102:7002 192.168.56.103:7003 192.168.56.104:7004 192.168.56.105:7005 192.168.56.106:7006
>>> Creating cluster
>>> Performing hash slots allocation on 6 nodes...
Using 3 masters:
192.168.56.101:7001
192.168.56.102:7002
192.168.56.103:7003
Adding replica 192.168.56.104:7004 to 192.168.56.101:7001
Adding replica 192.168.56.105:7005 to 192.168.56.102:7002
Adding replica 192.168.56.106:7006 to 192.168.56.103:7003
M: 455ebdfdaf1eebea64cab978683a50ce49fd915e 192.168.56.101:7001
slots:0-5460 (5461 slots) master
M: d40f7099e2725a94838ddc53d775a04f7b28d4b8 192.168.56.102:7002
slots:5461-10922 (5462 slots) master
M: a13f3b7390f20d43ee68b0a69e1e97b75427df13 192.168.56.103:7003
slots:10923-16383 (5461 slots) master
S: 523a99ecbb07b3d608d3fe17d63b07a487633cc9 192.168.56.104:7004
replicates 455ebdfdaf1eebea64cab978683a50ce49fd915e
S: db1126d54bf9f40f40342d188531cddf26f9f58d 192.168.56.105:7005
replicates d40f7099e2725a94838ddc53d775a04f7b28d4b8
S: ac4ebd89454e19f85cae1cfb8a273a6d8b306ce3 192.168.56.106:7006
replicates a13f3b7390f20d43ee68b0a69e1e97b75427df13
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.56.101:7001)
M: 455ebdfdaf1eebea64cab978683a50ce49fd915e 192.168.56.101:7001
slots:0-5460 (5461 slots) master
M: d40f7099e2725a94838ddc53d775a04f7b28d4b8 192.168.56.102:7002
slots:5461-10922 (5462 slots) master
M: a13f3b7390f20d43ee68b0a69e1e97b75427df13 192.168.56.103:7003
slots:10923-16383 (5461 slots) master
M: 523a99ecbb07b3d608d3fe17d63b07a487633cc9 192.168.56.104:7004
slots: (0 slots) master
replicates 455ebdfdaf1eebea64cab978683a50ce49fd915e
M: db1126d54bf9f40f40342d188531cddf26f9f58d 192.168.56.105:7005
slots: (0 slots) master
replicates d40f7099e2725a94838ddc53d775a04f7b28d4b8
M: ac4ebd89454e19f85cae1cfb8a273a6d8b306ce3 192.168.56.106:7006
slots: (0 slots) master
replicates a13f3b7390f20d43ee68b0a69e1e97b75427df13
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
=======================成功出现的信息 end============================