redis主从模式、哨兵模式（redis主从模式哨兵模式区别）

1. 配置简单的主从模式

准备好3个redis，现在我需要配置/opt/redis/redis-3.2.1-A为master，/opt/redis/redis-3.2.1-B、/opt/redis/redis-3.2.1-C为slave。

修改如下配置文件分别监听6379、16379、26379，然后两个slave都配置slaveof xx.xx.xx.xx 6379，其中xx.xx.xx.xx为master的IP（声明：我测试的环境为3个redis均在本机，即伪集群，真集群我还没有测试）

vi /opt/redis/redis-3.2.1-A/redis.conf vi /opt/redis/redis-3.2.1-B/redis.conf vi /opt/redis/redis-3.2.1-C/redis.conf

然后启动：

/opt/redis/redis-3.2.1-A/src/redis-server /opt/redis/redis-3.2.1-A/redis.conf & /opt/redis/redis-3.2.1-B/src/redis-server /opt/redis/redis-3.2.1-B/redis.conf & /opt/redis/redis-3.2.1-C/src/redis-server /opt/redis/redis-3.2.1-C/redis.conf &

然后客户连接测试，可以尝试用info查看各redis的信息，以及在master操作/读取数据、在slave读取数据。：

/opt/redis/redis-3.2.1-A/src/redis-cli -p 6379 /opt/redis/redis-3.2.1-B/src/redis-cli -p 16379 /opt/redis/redis-3.2.1-C/src/redis-cli -p 26379

2. 配置简单的哨兵模式

默认的sentinel.conf是这样的，另外自己加了简述：

[root@blog redis-3.2.1-A]# grep -v "^#" /opt/redis/redis-3.2.1-A/sentinel.conf | grep -v "^#34; port 26379 # 监听端口 dir /tmp sentinel monitor mymaster 127.0.0.1 6379 2 # 监视127.0.0.1:6379，判断此服务器为失效至少需要2个哨兵同意 sentinel down-after-milliseconds mymaster 30000 # 哨兵认为此服务器断线的时间 sentinel parallel-syncs mymaster 1 # 故障转移时，最多可以有多少slave从新master同步 sentinel failover-timeout mymaster 180000 # 故障转移超时时间

我配置了3个哨兵，只修改哨兵的端口和监视的master的IP、端口。（本人在阿里云上测试，启动时报端口已被使用，我加配了bind xx.xx.xx.xx，具体资料见[环境配置]阿里云ecs不支持redis-sentinel么？、[基础常识]在CentOS 6 运行 redis-sentinel 程序）

然后就启动了：

vi /opt/redis/redis-3.2.1-A/sentinel.conf vi /opt/redis/redis-3.2.1-B/sentinel.conf vi /opt/redis/redis-3.2.1-C/sentinel.conf /opt/redis/redis-3.2.1-A/src/redis-sentinel /opt/redis/redis-3.2.1-A/sentinel.conf & /opt/redis/redis-3.2.1-B/src/redis-sentinel /opt/redis/redis-3.2.1-B/sentinel.conf & /opt/redis/redis-3.2.1-C/src/redis-sentinel /opt/redis/redis-3.2.1-C/sentinel.conf &

进程如下：

[root@blog ~]# ps -ef | grep redis root 14788 13445 0 10:40 pts/1 00:00:00 /opt/redis/redis-3.2.1-A/src/redis-server xx.xx.xx.xx:6379 root 14793 13445 0 10:40 pts/1 00:00:00 /opt/redis/redis-3.2.1-B/src/redis-server xx.xx.xx.xx:16379 root 14799 13445 0 10:40 pts/1 00:00:00 /opt/redis/redis-3.2.1-C/src/redis-server xx.xx.xx.xx:26379 root 14916 14219 0 10:49 pts/4 00:00:00 /opt/redis/redis-3.2.1-A/src/redis-sentinel xx.xx.xx.xx:6380 [sentinel] root 14966 14943 0 10:50 pts/3 00:00:00 /opt/redis/redis-3.2.1-C/src/redis-sentinel xx.xx.xx.xx:26380 [sentinel] root 14971 14921 0 10:50 pts/2 00:00:00 /opt/redis/redis-3.2.1-B/src/redis-sentinel xx.xx.xx.xx:16380 [sentinel]

然后关闭master，会自动选其中一个slave为master，原master再次启动则为slave。

请注意，上述的redis.conf和sentinel.conf，Redis在运行中会生成、变更部分配置，比如，故障切换master后，/redis-3.2.1-A/redis.conf的最后有如下记录：

# Generated by CONFIG REWRITE slaveof xx.xx.xx.xx 16379

以下命令仅为本人备份使用，无参考意义：

vi /third_package/redis-3.2.1/redis_A.conf vi /third_package/redis-3.2.1/redis_B.conf vi /third_package/redis-3.2.1/redis_C.conf cp redis_A.conf /opt/redis/redis-3.2.1-A/redis.conf cp redis_B.conf /opt/redis/redis-3.2.1-B/redis.conf cp redis_C.conf /opt/redis/redis-3.2.1-C/redis.conf /opt/redis/redis-3.2.1-A/src/redis-server /opt/redis/redis-3.2.1-A/redis.conf & /opt/redis/redis-3.2.1-B/src/redis-server /opt/redis/redis-3.2.1-B/redis.conf & /opt/redis/redis-3.2.1-C/src/redis-server /opt/redis/redis-3.2.1-C/redis.conf & /opt/redis/redis-3.2.1-A/src/redis-cli -p 6379 /opt/redis/redis-3.2.1-B/src/redis-cli -p 16379 /opt/redis/redis-3.2.1-C/src/redis-cli -p 26379 vi /third_package/redis-3.2.1/sentinel_A.conf vi /third_package/redis-3.2.1/sentinel_B.conf vi /third_package/redis-3.2.1/sentinel_C.conf cp sentinel_A.conf /opt/redis/redis-3.2.1-A/sentinel.conf cp sentinel_B.conf /opt/redis/redis-3.2.1-B/sentinel.conf cp sentinel_C.conf /opt/redis/redis-3.2.1-C/sentinel.conf /opt/redis/redis-3.2.1-A/src/redis-sentinel /opt/redis/redis-3.2.1-A/sentinel.conf & /opt/redis/redis-3.2.1-B/src/redis-sentinel /opt/redis/redis-3.2.1-B/sentinel.conf & /opt/redis/redis-3.2.1-C/src/redis-sentinel /opt/redis/redis-3.2.1-C/sentinel.conf & ps -ef | grep redis