Redis Cluster deployment

Redis Cluster Deployment

1. Installation of Redis 3.0.1, see Redis 3.0.1 Installation and configuration

2. Create a Directory

Mkdir-p/usr/local/redis/7000

3. Copying files

cd/tmp# Copy the default configuration document CP redis-3.0.1/redis.conf/usr/local/redis/redis.default.conf# Copy the compiled server to the running directory CP REDIS-3.0.1/ Src/redis-server/usr/local/redis/7000/

4. Create a standalone profile

#在7000目录下建立redis的配置文档vim/usr/local/redis/7000/redis.conf

#/usr/local/redis/7000/redis.confinclude/usr/local/redis/redis.default.confpidfile/var/run/redis-7000.pidport 7000cluster-enabled yescluster-config-file redis-node-7000.confcluster-node-timeout 5000appendonly Yes

5. Copy the Run Directory

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. Modify the port and file name of the corresponding profile

7. Create a startup script/usr/local/redis/redis-start.sh

#!/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. Add Execute Permissions

chmod a+x redis-start.sh

9. Launch six Redis instances

./redis-start.sh

Configuring the Cluster

1. Install Ruby

Yum Install ruby-devel.x86_64

2. Installing the Redis Gem

Gem Install Redis

3. Using scripts to create a cluster mechanism

When create, the parameter--replicas 1 means that each master is assigned a salve, such as an example, 3 Master 3 Salve

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

>>> creating clusterconnecting to node 127.0.0.1:7000: okconnecting  to node 127.0.0.1:7001: OKConnecting to node 127.0.0.1:7002:  OKCONNECTING TO NODE 127.0.0.1:7003: OKCONNECTING TO NODE 127.0.0.1:7004:  OKConnecting to node 127.0.0.1:7005: OK>>> Performing hash  Slots allocation on 6 nodes ... Using 6 masters :127.0.0.1:7000127.0.0.1:7001127.0.0.1:7002127.0.0.1:7003127.0.0.1:7004127.0.0.1:7005m:  886a2c0feade15ea70d06ba1b36d081b8126493c 127.0.0.1:7000slots:0-2730  (2731 slots)  masterM:  33ad339351b1a4b4e5102afe3b07b872a8e6f54d 127.0.0.1:7001slots:2731-5460  (2730 slots)   masterm: 6dc748d61238a221cc7bd7fdcc6b56d4dfa81a22 127.0.0.1:7002slots:5461-8191  (2731  Slots)  masterm: ea21e187cd635a6891ddb3b70db3cae31293917b 127.0.0.1:7003slots:8192-10922  (2731 slots)  masterM: 17b66eae8d2f8570ef158c6f4f426989726794da  127.0.0.1:7004slots:10923-13652  (2730 slots)  masterM:  f7946e662656d2f234e35d108e1ac28ccf6ebc34 127.0.0.1:7005slots:13653-16383  (2731 slots)   mastercan i set the above configuration?  (type  ' yes '  to accept):  yes>>> nodes configuration updated>>> assign a different  config epoch to each node8793:M 08 Jun 15:45:40.140 #  configepoch set to 1 via cluster set-config-epoch8794:m 08 jun  15:45:40.140 # configepoch set to 2 via cluster set-config-epoch8795:m  08 jun 15:45:40.140 # configepoch set to 3 via cluster  set-config-epoch8796:m 08 jun 15:45:40.141 # configepoch set to 4 via cluster set-config-epoch8797:m 08  Jun 15:45:40.141 # configEpoch set to 5 via CLUSTER  Set-config-epoch8798:m 08 jun 15:45:40.141 # configepoch set to 6  via cluster set-config-epoch>>> sending cluster meet messages  to join the cluster8793:m 08 jun 15:45:40.157 # ip address  for this node updated to 127.0.0.18795:m 08 jun 15:45:40.190  # ip address for this node updated to 127.0.0.18796:m 08  jun 15:45:40.190 # ip address for this node updated to  127.0.0.18797:M 08 Jun 15:45:40.190 # IP address for this  node updated to 127.0.0.18794:m 08 jun 15:45:40.290 # ip address for this node updated  to 127.0.0.18798:M 08 Jun 15:45:40.290 # IP address for  This node updated to 127.0.0.1waiting for the cluster to join .... 8793:m 08 jun 15:45:44.279 # cluster state changed: ok8794:m 08  Jun 15:45:44.508 # Cluster state changed: ok8795:M 08 Jun  15:45:44.545 # cluster state changed: ok8796:m 08 jun 15:45:44.697  # Cluster state changed: ok8797:M 08 Jun 15:45:44.923 #  cluster state changed: ok8798: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:7000slots:0-2730  (2731 slots)  masterM:  33ad339351b1a4b4e5102afe3b07b872a8e6f54d 127.0.0.1:7001slots:2731-5460  (2730 slots)   masterm: 6dc748d61238a221cc7bd7fdcc6b56d4dfa81a22 127.0.0.1:7002slots:5461-8191  (2731  Slots)  masterM: ea21e187cd635a6891ddb3b70db3cae31293917b 127.0.0.1:7003slots:8192-10922  ( 2731 slots)  masterm: 17b66eae8d2f8570ef158c6f4f426989726794da 127.0.0.1:7004slots :10923-13652  (2730 slots)  masterM: f7946e662656d2f234e35d108e1ac28ccf6ebc34  127.0.0.1:7005slots:13653-16383  (2731 slots)  master[OK] All nodes agree  about slots configuration.>>> check for open slots...>>>  Check slots coverage ... [Ok] all 16384 slots covered.

This article is from the SQL Server deep dives blog, so be sure to keep this source http://ultrasql.blog.51cto.com/9591438/1659729

Redis Cluster deployment