/etc/sentinel.conf config error! about redis-sentinel-docker HOT 3 CLOSED

Hi @xjzrc, thank you for pointing out this issue.

I vaguely remember that the usage of SLAVES was added, because of ECS. I need to investigate a little bit more. Meantime, you should avoid using SLAVES configuration and setup slaves correctly e.g.

version: '3'

services:
  master:
    image: redis:4.0.10-alpine

  slave_1:
    image: redis:4.0.10-alpine
    command: redis-server --slaveof master 6379
    depends_on:
      - master

  slave_2:
    image: redis:4.0.10-alpine
    command: redis-server --slaveof master 6379
    depends_on:
      - master

  sentinel_1:
    image: s7anley/redis-sentinel-docker:4.0.10
    ports:
      - 26379:26379
    environment:
      - MASTER_NAME=mymaster
      - QUORUM=2
      - MASTER=master
    depends_on:
      - master

$ docker exec -ti redissentineldocker_sentinel_1_1 redis-cli -p 26379 info sentinel
# Sentinel
sentinel_masters:1
sentinel_tilt:0
sentinel_running_scripts:0
sentinel_scripts_queue_length:0
sentinel_simulate_failure_flags:0
master0:name=mymaster,status=ok,address=172.19.0.2:6379,slaves=2,sentinels=1

from redis-sentinel-docker.

Thanks for your reply！I see you .

from redis-sentinel-docker.

Use-case for SLAVES is when you Redis instances aren't accessible in single network e.g. in ECS it was not possible to use the IP address of slave, because they were pointing to internal IP address allocated by docker on the single machine, not in the whole cluster.

from redis-sentinel-docker.