奇闻: docker搭建的redis哨兵集群会导致redis集群的master服务死掉

Question

我在docker上通过docker-compose搭建了一个一主二从的redis集群.搭建成功后集群正常运行

version: '2'
services:
  master:
    image: redis
    container_name: redis-1
    command: redis-server --requirepass 123456 --masterauth 123456
    ports:
      - 6379:6379
    volumes:
      - /opt/soft/health-care/redis/redis-1/data:/data
      - /opt/soft/health-care/redis/redis-1/conf:/etc/redis/conf
  slave1:
    image: redis
    container_name: redis-2
    ports:
      - 6380:6379
    volumes:
      - /opt/soft/health-care/redis/redis-2/data:/data
      - /opt/soft/health-care/redis/redis-2/conf:/etc/redis/conf
    command: redis-server --slaveof redis-1 6379 --requirepass 123456 --masterauth 123456
  slave2:
    image: redis
    container_name: redis-3
    ports:
      - 6381:6379
    volumes:
      - /opt/soft/health-care/redis/redis-3/data:/data
      - /opt/soft/health-care/redis/redis-3/conf:/etc/redis/conf
    command: redis-server --slaveof redis-1 6379 --requirepass 123456 --masterauth 123456

通过docker inspect redis-1查询得知redis-1的ip为

之后,又通过docker-compose搭建了三个哨兵组成的哨兵集群

version: '2'
services:
  sentinel1:
    image: redis
    container_name: redis-sentinel-1
    ports:
      - 26379:26379
    command: redis-sentinel /usr/local/etc/redis/sentinel.conf
    volumes:
      - /opt/soft/health-care/redis-sentinel/sentinel-1/conf/sentinel.conf:/usr/local/etc/redis/sentinel.conf
  sentinel2:
    image: redis
    container_name: redis-sentinel-2
    ports:
    - 26380:26379
    command: redis-sentinel /usr/local/etc/redis/sentinel.conf
    volumes:
      - /opt/soft/health-care/redis-sentinel/sentinel-2/conf/sentinel.conf:/usr/local/etc/redis/sentinel.conf
  sentinel3:
    image: redis
    container_name: redis-sentinel-3
    ports:
      - 26381:26379
    command: redis-sentinel /usr/local/etc/redis/sentinel.conf
    volumes:
      - /opt/soft/health-care/redis-sentinel/sentinel-3/conf/sentinel.conf:/usr/local/etc/redis/sentinel.conf
networks:
  default:
    external:
      name: docker-compose_default

哨兵配置文件如下:

port 26379
dir /tmp
# 172.19.0.4-> 是redis集群的master服务ip
sentinel monitor mymaster 172.19.0.4 6379 2
sentinel auth-pass mymaster 123456
sentinel down-after-milliseconds mymaster 30000
sentinel parallel-syncs mymaster 1
sentinel failover-timeout mymaster 180000
sentinel deny-scripts-reconfig yes

问题出现在哨兵集群的启动:

哨兵集群启动之后,会导致redis集群的master状态变为:  master_link_status:down

 

Answer 1

不知道你这个问题是否已经解决, 如果还没有解决的话:

• 这有个类似的问题, 你可以参考下: https://ask.csdn.net/questions/7492151
• 你也可以参考下这篇文章：解决自己在docker中设置redis密码不生效的问题
• 除此之外, 这篇博客: Docker搭建Redis哨兵模式集群中的 2.1 先按照如下链接中方法搭建一个一主二从的Redis集群，其中redis-master1是主服务器，redis-salve11和redis-salve22是从服务器。 部分也许能够解决你的问题, 你可以仔细阅读以下内容或者直接跳转源博客中阅读:
  
  Docker搭建Redis主从复制集群https://blog.csdn.net/qq_43753724/article/details/120390533?spm=1001.2014.3001.5501
  

如果你已经解决了该问题, 非常希望你能够分享一下解决方案, 写成博客, 将相关链接放在评论区, 以帮助更多的人 ^-^