哨兵:在redis里监控服务,在主从复制结构中,当主服务器宕机,哨兵可以监控到服务宕机,并且在服务器中选举产生一个新的主服务器。
选举多个哨兵,一个是高可用,另一个原因是投票,当都投票到一个说明这个服务器宕机。少数服从多数
systemctl restart docker
清理容器docker rm -f $(docker ps -aq)
进入容器docker exec -it redis6379 redis-cli
查看集群信息,默认是主服务器info replication
启动两个从服务器 启动redis6380容器,作为 redis6379 的从服务器启动 –port 和 --slaveof 是 redis-server 命令的参数docker run -d --name redis6380 --net=host --restart=always redis
redis-server --port 6380 --slaveof 192.168.64.150 6379
docker run -d --name redis6381 --net=host --restart=always redis
redis-server --port 6381 --slaveof 192.168.64.150 6379
docker exec -it redis6379 redis-cli
info replication
docker exec -it redis6380 redis-cli -p 6380
info replication
docker exec -it redis6381 redis-cli -p 6381
启动哨兵info replication
哨兵的配置文件
mkdir /opt/sentinel/
cd /opt/sentinel/
cat <5000.conf port 5000 sentinel monitor mymaster
192.168.64.150 6379 2 sentinel down-after-milliseconds mymaster 5000 sentinel failover-timeout mymaster 60000 sentinel parallel-syncs
mymaster 1 EOFcat <5001.conf port 5001 sentinel monitor mymaster
192.168.64.150 6379 2 sentinel down-after-milliseconds mymaster 5000 sentinel failover-timeout mymaster 60000 sentinel parallel-syncs
mymaster 1 EOFcat <5002.conf port 5002 sentinel monitor mymaster
192.168.64.150 6379 2 sentinel down-after-milliseconds mymaster 5000 sentinel failover-timeout mymaster 60000 sentinel parallel-syncs
mymaster 1 EOF
启动三个哨兵
进入一个哨兵容器,查看它监控的主从服务器和其他哨兵docker run -d --name sentinel5000
-v /opt/sentinel/5000.conf:/sentinel.conf
–net=host redis redis-sentinel /sentinel.confdocker run -d --name sentinel5001
-v /opt/sentinel/5001.conf:/sentinel.conf
–net=host redis redis-sentinel /sentinel.confdocker run -d --name sentinel5002
-v /opt/sentinel/5002.conf:/sentinel.conf
–net=host redis redis-sentinel /sentinel.conf
停止主服务器,测试主服务器重新选举 停止主服务器docker exec -it sentinel5000 redis-cli -p 5000 sentinel master
mymaster sentinel slaves mymaster sentinel sentinels mymaster
在哨兵日志中查看服务器切换日志: +switch-master mymaster 192.168.64.150 6379 192.168.64.150 6381docker stop redis6379
查看 6380 和 6381 服务器的角色变化docker logs sentinel5000
重新启动6379,不会把6379切换成主服务器,而是作为从服务器docker exec -it redis6380 redis-cli -p 6380
info replication
docker exec -it redis6381 redis-cli -p 6381
info replication
客户端api连接哨兵存取数据docker start redis6379
docker exec -it redis6379 redis-cli
info replication
Set sets = new HashSet<>();
sets.add(“192.168.64.151:5000”);
sets.add(“192.168.64.151:5001”);
sets.add(“192.168.64.151:5002”);JedisPoolConfig poolConfig = new JedisPoolConfig(); JedisSentinelPool pool = new JedisSentinelPool("mymaster",sets,poolConfig); Jedis jedis = pool.getResource(); jedis.set("a", "aaaaaaa"); System.out.println(jedis.get("a")); jedis.close();



