Redis 集群部署( 转载)

352262

　　Redis 集群部署
　　
　　1.安装redis 3.0.1，参见《Redis 3.0.1 安装和配置》
　　2.创建目录
1mkdir -p /usr/local/redis/7000　　3.复制文件
12345cd /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.建立独立配置文件
12#在7000目录下建立redis的配置文档vim /usr/local/redis/7000/redis.conf12345678#/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.复制运行目录
123456cd /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
1234567#!/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.添加执行权限
1chmod a+x redis-start.sh　　9.启动六个redis实例
1./redis-start.sh　　配置集群
　　1.安装ruby
1yum install ruby-devel.x86_64　　2.安装redis gem
1gem install redis　　3.使用脚本建立集群机制
　　在create的时候,加上参数--replicas 1 表示为每个master分配一个salve,如例子,则是3个master 3个salve
12cd /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:7005123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566>>> 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.　　本文出自 “SQL Server Deep Dives” 博客，请务必保留此出处http://ultrasql.blog.51cto.com/9591438/1659729