I configured it using docker-compose.
docker-compose.yaml
`version: '3.9'
networks: app-tier: driver: bridge
services: redis: image: 'bitnami/redis:latest' environment: - REDIS_REPLICATION_MODE=master - ALLOW_EMPTY_PASSWORD=yes networks: - app-tier ports: - 6379:6379 redis-slave-1: image: 'bitnami/redis:latest' environment: - REDIS_REPLICATION_MODE=slave - REDIS_MASTER_HOST=redis - ALLOW_EMPTY_PASSWORD=yes ports: - 6479:6379 depends_on: - redis networks: - app-tier redis-slave-2: image: 'bitnami/redis:latest' environment: - REDIS_REPLICATION_MODE=slave - REDIS_MASTER_HOST=redis - ALLOW_EMPTY_PASSWORD=yes ports: - 6579:6379 depends_on: - redis networks: - app-tier
redis-sentinel: image: 'bitnami/redis-sentinel:latest' environment: - REDIS_SENTINEL_DOWN_AFTER_MILLISECONDS=3000 - REDIS_MASTER_HOST=redis - REDIS_MASTER_PORT_NUMBER=6379 - REDIS_MASTER_SET=mymaster - REDIS_SENTINEL_QUORUM=2 depends_on: - redis - redis-slave-1 - redis-slave-2 ports: - '26379-26381:26379' networks: - app-tier`
then I downed master node.
and that, sentinel node logs like below
As a result, fail-over doesn't work. only this message repeated.
[Failed to resolve hostname 'redis']
But, I did not give up, I tested it redis 6.2.6 version.
like below, docker-compose.yml
`version: '2'
services:
# master : bitnami/redis:6.2.6 redis-master: hostname: redis-master container_name: redis-master image: bitnami/redis:6.2.6 environment: - REDIS_REPLICATION_MODE=master - ALLOW_EMPTY_PASSWORD=yes ports: - 6379:6379
# slave1 : bitnami/redis:6.2.6 redis-slave-1: hostname: redis-slave-1 container_name: redis-slave-1 image: bitnami/redis:6.2.6 environment: - REDIS_REPLICATION_MODE=slave - REDIS_MASTER_HOST=redis-master - ALLOW_EMPTY_PASSWORD=yes ports: - 6480:6379 depends_on: - redis-master
# slave2 : bitnami/redis:6.2.6 redis-slave-2: hostname: redis-slave-2 container_name: redis-slave-2 image: bitnami/redis:6.2.6 environment: - REDIS_REPLICATION_MODE=slave - REDIS_MASTER_HOST=redis-master - ALLOW_EMPTY_PASSWORD=yes ports: - 6481:6379 depends_on: - redis-master - redis-slave-1
# sentinel1 : bitnami/redis-sentinel:6.2.6 redis-sentinel-1: hostname: redis-sentinel-1 container_name: redis-sentinel-1 image: bitnami/redis-sentinel:6.2.6 environment: - REDIS_SENTINEL_DOWN_AFTER_MILLISECONDS=3000 - REDIS_MASTER_HOST=redis-master - REDIS_MASTER_PORT_NUMBER=6379 - REDIS_MASTER_SET=master-name - REDIS_SENTINEL_QUORUM=2 depends_on: - redis-master - redis-slave-1 - redis-slave-2 ports: - 26379:26379
# sentinel2 : bitnami/redis-sentinel:6.2.6 redis-sentinel-2: hostname: redis-sentinel-2 container_name: redis-sentinel-2 image: bitnami/redis-sentinel:6.2.6 environment: - REDIS_SENTINEL_DOWN_AFTER_MILLISECONDS=3000 - REDIS_MASTER_HOST=redis-master - REDIS_MASTER_PORT_NUMBER=6379 - REDIS_MASTER_SET=master-name - REDIS_SENTINEL_QUORUM=2 depends_on: - redis-master - redis-slave-1 - redis-slave-2 ports: - 26380:26379
# sentinel3 : bitnami/redis-sentinel:6.2.6 redis-sentinel-3: hostname: redis-sentinel-3 container_name: redis-sentinel-3 image: bitnami/redis-sentinel:6.2.6 environment: - REDIS_SENTINEL_DOWN_AFTER_MILLISECONDS=3000 - REDIS_MASTER_HOST=redis-master - REDIS_MASTER_PORT_NUMBER=6379 - REDIS_MASTER_SET=master-name - REDIS_SENTINEL_QUORUM=2 depends_on: - redis-master - redis-slave-1 - redis-slave-2 ports: - 26381:26379`
fail-over work completed.
I don't understand why that problem occured at latest version.
Maybe, there are some configurations that I shoule do?
Comment From: JmKanmo
sorry, that repo is bitnami/redis. I close it.