Redis cluster with Docker Compose
Using Docker Compose to setup a redis cluster for testing sentinel failover.
This project is inspired by the project of https://github.com/mdevilliers/docker-rediscluster
Install Docker and Docker Compose in testing environment
Optional: Install the redis-cli. E.g. with following command in Ubuntu
apt-get install redis-server
The tempalte defines the topology of the Redis cluster
redismaster:
image: redis:2.8
redisslave:
image: redis:2.8
links:
- redismaster
sentinel:
build: sentinel
links:
- redismaster
- redisslave
- redisconfig
redisconfig:
build: redis-config
links:
- redismaster
- redisslave
There are following nodes in the cluster,
- redismaster: Redis master
- redisslave: Redis slave
- sentinel: Sentinel instance
- redisconfig: Redis CLI to config the master/slave which will exit after configuraion
The sentinels are configured with a "mymaster" instance with the following properties -
sentinel monitor mymaster redismaster 6379 2
sentinel down-after-milliseconds mymaster 1000
sentinel parallel-syncs mymaster 1
sentinel failover-timeout mymaster 1000
The details could be found in sentinel/sentinel.conf
Start the redis cluster
docker-compose up
Check the status of redis cluster
docker-compose ps
The result is
Name Command State Ports
rediscluster_redisconfig_1 /entrypoint.sh /bin/sh -c ... Exit 0
rediscluster_redismaster_1 /entrypoint.sh redis-server Up 6379/tcp
rediscluster_redisslave_1 /entrypoint.sh redis-server Up 6379/tcp
rediscluster_sentinel_1 redis-sentinel /etc/redis/ ... Up 26379/tcp
Scale out the instance number of sentinel
docker-compose scale sentinel=3
Check the status of redis cluster
docker-compose ps
The result is
Name Command State Ports
rediscluster_redisconfig_1 /entrypoint.sh /bin/sh -c ... Exit 0
rediscluster_redismaster_1 /entrypoint.sh redis-server Up 6379/tcp
rediscluster_redisslave_1 /entrypoint.sh redis-server Up 6379/tcp
rediscluster_sentinel_1 redis-sentinel /etc/redis/ ... Up 26379/tcp
rediscluster_sentinel_2 redis-sentinel /etc/redis/ ... Up 26379/tcp
rediscluster_sentinel_3 redis-sentinel /etc/redis/ ... Up 26379/tcp
Execut the test scripts
./test.sh
to simulate stop and recover the Redis master. And you will see the master is switched to slave automatically.
Or, you can do the test manually to pause/unpause redis server through
docker pause rediscluster_redismaster_1
docker unpause rediscluster_redismaster_1
And get the sentinel infomation with following commands
SENTINEL_IP=$(docker inspect --format '{{ .NetworkSettings.IPAddress }}' rediscluster_sentinel_1)
redis-cli -h $SENTINEL_IP -p 26379 info Sentinel
https://github.com/mdevilliers/docker-rediscluster
[https://registry.hub.docker.com/u/joshula/redis-sentinel/] 2
- Li Yi ([email protected])
- Ty Alexander ([email protected])
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent