Redis哨兵配置(官网简单实现)

Posted 2022-11-28 Java小周

redis 哨兵

redis主从复制结构中，当主服务器宕机，哨兵可以监控到服务宕机，从从服务器中选举产生一个新的主服务器

搭建主从服务器 – 一主两从

先清空其他容器（全部启动大概0.3~0.5个G，性能好的请忽略）

docker rm -f $(docker ps -aq)

启动主服务器，正常启动，没有特殊设置
 

docker run -d --name redis6379 --net=host --restart=always redis 

docker exec -it redis6379 redis-cli
> info replication

启动两个从服务器

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 <<EOF>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
EOF


cat <<EOF>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
EOF


cat <<EOF>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.conf


docker run -d --name sentinel5001 \\
-v /opt/sentinel/5001.conf:/sentinel.conf \\
--net=host \\
redis redis-sentinel /sentinel.conf


docker 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

停止主服务器，测试主服务器重新选举

docker stop redis6379

查看哨兵日志，可以看到主服务器从6379切换到6381上了

docker logs sentinel5000

再次查看主从关系

docker exec -it redis6380 redis-cli -p 6380
> info replication

docker exec -it redis6381 redis-cli -p 6381
> info replication

重新启动6379（不会把6379切换成主服务器，而是作为从服务器）

docker start redis6379
docker exec -it redis6379 redis-cli
> info replication

模拟客户端进行测试

package test;

import redis.clients.jedis.Jedis;
import redis.clients.jedis.JedisSentinelPool;

import java.util.HashSet;

public class TestSentinel 
    public static void main(String[] args) 
        HashSet<String> set = new HashSet<>();
        set.add("192.168.64.150:5000");
        set.add("192.168.64.150:5001");
        set.add("192.168.64.150:5002");

        JedisSentinelPool pool = new JedisSentinelPool("mymaster", set);
        Jedis j = pool.getResource();
        j.set("k1","v1");
        String v = j.get("k1");
        System.out.println(v);
    

Redis哨兵到这里就结束了，感谢关注，点赞加收藏

关注Java_小周最新动态，查看更多技术点