Redis 集群部署( 转载)
Redis 集群部署
1.安装redis 3.0.1，参见《Redis 3.0.1 安装和配置》
2.创建目录
|
1
|
mkdir
-p
/usr/local/redis/7000
|
3.复制文件
|
1
2
3
4
5
|
cd
/tmp
#复制默认的配置文档
cp
redis-3.0.1
/redis
.conf
/usr/local/redis/redis
.default.conf
#把编译好的server复制到运行目录
cp
redis-3.0.1
/src/redis-server
/usr/local/redis/7000/
|
4.建立独立配置文件
|
1
2
|
#在7000目录下建立redis的配置文档
vim
/usr/local/redis/7000/redis
.conf
|
|
1
2
3
4
5
6
7
8
|
#/usr/local/redis/7000/redis.conf
include /usr/local/redis/redis.default.conf
pidfile /var/run/redis-7000.pid
port 7000
cluster-enabled yes
cluster-config-file redis-node-7000.conf
cluster-node-timeout 5000
appendonly yes
|
5.复制运行目录
|
1
2
3
4
5
6
|
cd
/usr/local/redis/
cp
-R 7000/ 7001/
cp
-R 7000/ 7002/
cp
-R 7000/ 7003/
cp
-R 7000/ 7004/
cp
-R 7000/ 7005/
|
6.修改相应配置文件的端口和文件名
7.建立启动脚本/usr/local/redis/redis-start.sh
|
1
2
3
4
5
6
7
|
#!/bin/sh
/usr/local/redis/7000/redis-server
/usr/local/redis/7000/redis
.conf &
/usr/local/redis/7001/redis-server
/usr/local/redis/7001/redis
.conf &
/usr/local/redis/7002/redis-server
/usr/local/redis/7002/redis
.conf &
/usr/local/redis/7003/redis-server
/usr/local/redis/7003/redis
.conf &
/usr/local/redis/7004/redis-server
/usr/local/redis/7004/redis
.conf &
/usr/local/redis/7005/redis-server
/usr/local/redis/7005/redis
.conf &
|
8.添加执行权限
|
1
|
chmod
a+x redis-start.sh
|
9.启动六个redis实例
|
1
|
.
/redis-start
.sh
|
配置集群
1.安装ruby
|
1
|
yum
install
ruby-devel.x86_64
|
2.安装redis gem
|
1
|
gem
install
redis
|
3.使用脚本建立集群机制
在create的时候,加上参数--replicas 1 表示为每个master分配一个salve,如例子,则是3个master 3个salve
|
1
2
|
cd
/tmp/redis-3
.0.1
/src/
.
/redis-trib
.rb create --replicas 1 127.0.0.1:7000 127.0.0.1:7001 127.0.0.1:7002 127.0.0.1:7003 127.0.0.1:7004 127.0.0.1:7005
|
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
|
>>> Creating cluster
Connecting to node 127.0.0.1:7000: OK
Connecting to node 127.0.0.1:7001: OK
Connecting to node 127.0.0.1:7002: OK
Connecting to node 127.0.0.1:7003: OK
Connecting to node 127.0.0.1:7004: OK
Connecting to node 127.0.0.1:7005: OK
>>> Performing hash slots allocation on 6 nodes...
Using 6 masters:
127.0.0.1:7000
127.0.0.1:7001
127.0.0.1:7002
127.0.0.1:7003
127.0.0.1:7004
127.0.0.1:7005
M: 886a2c0feade15ea70d06ba1b36d081b8126493c 127.0.0.1:7000
slots:0-2730 (2731 slots) master
M: 33ad339351b1a4b4e5102afe3b07b872a8e6f54d 127.0.0.1:7001
slots:2731-5460 (2730 slots) master
M: 6dc748d61238a221cc7bd7fdcc6b56d4dfa81a22 127.0.0.1:7002
slots:5461-8191 (2731 slots) master
M: ea21e187cd635a6891ddb3b70db3cae31293917b 127.0.0.1:7003
slots:8192-10922 (2731 slots) master
M: 17b66eae8d2f8570ef158c6f4f426989726794da 127.0.0.1:7004
slots:10923-13652 (2730 slots) master
M: f7946e662656d2f234e35d108e1ac28ccf6ebc34 127.0.0.1:7005
slots:13653-16383 (2731 slots) master
Can I set the above configuration? (type 'yes' to accept): yes
>>> Nodes configuration updated
>>> Assign a different config epoch to each node
8793:M 08 Jun 15:45:40.140 # configEpoch set to 1 via CLUSTER SET-CONFIG-EPOCH
8794:M 08 Jun 15:45:40.140 # configEpoch set to 2 via CLUSTER SET-CONFIG-EPOCH
8795:M 08 Jun 15:45:40.140 # configEpoch set to 3 via CLUSTER SET-CONFIG-EPOCH
8796:M 08 Jun 15:45:40.141 # configEpoch set to 4 via CLUSTER SET-CONFIG-EPOCH
8797:M 08 Jun 15:45:40.141 # configEpoch set to 5 via CLUSTER SET-CONFIG-EPOCH
8798:M 08 Jun 15:45:40.141 # configEpoch set to 6 via CLUSTER SET-CONFIG-EPOCH
>>> Sending CLUSTER MEET messages to join the cluster
8793:M 08 Jun 15:45:40.157 # IP address for this node updated to 127.0.0.1
8795:M 08 Jun 15:45:40.190 # IP address for this node updated to 127.0.0.1
8796:M 08 Jun 15:45:40.190 # IP address for this node updated to 127.0.0.1
8797:M 08 Jun 15:45:40.190 # IP address for this node updated to 127.0.0.1
8794:M 08 Jun 15:45:40.290 # IP address for this node updated to 127.0.0.1
8798:M 08 Jun 15:45:40.290 # IP address for this node updated to 127.0.0.1
Waiting for the cluster to join....8793:M 08 Jun 15:45:44.279 # Cluster state changed: ok
8794:M 08 Jun 15:45:44.508 # Cluster state changed: ok
8795:M 08 Jun 15:45:44.545 # Cluster state changed: ok
8796:M 08 Jun 15:45:44.697 # Cluster state changed: ok
8797:M 08 Jun 15:45:44.923 # Cluster state changed: ok
8798:M 08 Jun 15:45:45.002 # Cluster state changed: ok
>>> Performing Cluster Check (using node 127.0.0.1:7000)
M: 886a2c0feade15ea70d06ba1b36d081b8126493c 127.0.0.1:7000
slots:0-2730 (2731 slots) master
M: 33ad339351b1a4b4e5102afe3b07b872a8e6f54d 127.0.0.1:7001
slots:2731-5460 (2730 slots) master
M: 6dc748d61238a221cc7bd7fdcc6b56d4dfa81a22 127.0.0.1:7002
slots:5461-8191 (2731 slots) master
M: ea21e187cd635a6891ddb3b70db3cae31293917b 127.0.0.1:7003
slots:8192-10922 (2731 slots) master
M: 17b66eae8d2f8570ef158c6f4f426989726794da 127.0.0.1:7004
slots:10923-13652 (2730 slots) master
M: f7946e662656d2f234e35d108e1ac28ccf6ebc34 127.0.0.1:7005
slots:13653-16383 (2731 slots) master
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
|