redis的集群方法大概有三种:
1.redis cluster集群方案;
2 .master/slave主从方案;
3.哨兵模式来进行主从替换以及故障恢复。
sentinel系统可以监听一个或多个redis服务,以及master的从服务器,当master宕机的时候,sentinel可以主动从slave中拉起一个升级为master服务
创建文件夹 redis-sentinel文件夹 ,进入redis-sentinel;
创建sentinel,进入sentinel;
建立sentinel.conf配置文件:
sentinel monitor mymaster redis-master 6379 2
sentinel down-after-milliseconds mymaster 5000
sentinel parallel-syncs mymaster 1
sentinel failover-timeout mymaster 5000
监控主服务器的6379端口并且起了两个实例,如果哨兵5秒内没有收到master的心跳,sentinel
会觉得master已经宕机了,如何超过5秒连接不上master,则会在slave中选择最优的升级为master的一个角色转换
建立sentinel-entrypoint.sh脚本文件:
#!/bin/sh
sed -i "s/$SENTINEL_QUORUM/$SENTINEL_QUORUM/g" /etc/redis/sentinel.conf
sed -i "s/$SENTINEL_DOWN_AFTER/$SENTINEL_DOWN_AFTER/g" /etc/redis/sentinel.conf
sed -i "s/$SENTINEL_FAILOVER/$SENTINEL_FAILOVER/g" /etc/redis/sentinel.conf
exec docker-entrypoint.sh redis-server /etc/redis/sentinel.conf --sentinel
该脚本文件会对配置文件进行同步,用来启动哨兵
然后我们来建立Dockerfile指定基础镜像,同时拷贝配置文件到镜像内部:
FROM redis
EXPOSE 26379
ADD sentinel.conf /etc/redis/sentinel.conf
RUN chown redis:redis /etc/redis/sentinel.conf
COPY sentinel-entrypoint.sh /usr/local/bin/
RUN chmod +x /usr/local/bin/sentinel-entrypoint.sh
ENTRYPOINT ["sentinel-entrypoint.sh"]
最后返回redis-sentinel,创建docker-compose.yml配置文件:
version: '2'
networks:
app-tier:
driver: bridge
services:
redis:
image: 'bitnami/redis:latest'
environment:
- REDIS_REPLICATION_MODE=master
- REDIS_PASSWORD=""
networks:
- app-tier
ports:
- '6379:6379'
redis-slave:
image: 'bitnami/redis:latest'
environment:
- REDIS_REPLICATION_MODE=slave
- REDIS_MASTER_HOST=redis
- REDIS_MASTER_PASSWORD=""
- REDIS_PASSWORD=""
ports:
- '6380:6379'
depends_on:
- redis
networks:
- app-tier
redis-slave2:
image: 'bitnami/redis:latest'
environment:
- REDIS_REPLICATION_MODE=slave
- REDIS_MASTER_HOST=redis
- REDIS_MASTER_PASSWORD=""
- REDIS_PASSWORD=""
ports:
- '6381:6379'
depends_on:
- redis
networks:
- app-tier
redis-sentinel:
image: 'bitnami/redis-sentinel:latest'
environment:
- REDIS_MASTER_PASSWORD=""
depends_on:
- redis
- redis-slave
- redis-slave2
ports:
- '26379-26381:26379'
networks:
- app-tier
意思是,一共开启了三个redis服务,6379,6380,6381端口,一主两从,并且会有哨兵实例来监控它们,最后项目结构是这样的
进入redis-sentinel,cmd,启动服务:
docker-compose up --scale redis-sentinel=3
此时我们可以测一下同步是否成功,分别开三个命令行窗口登录到redis,redis-cli -p 6379,redis-cli -p 6380,redis-cli -p 6381
在主库6379中set 1 123,然后分别在从库get 1,
成功后,手动停止master服务,
docker stop 6e2c3(6379容器id)
此时可以从之前连接6379的命令行内看一下是否连接正常,set 2 2,如果失败则代表master已经宕机了,打开6380和6381输入info看一下role(角色)是否有一个发生了改变