Redis' official documentation (https://redis.io/topics/cluster-tutorial) recommends a setup with 6 dedicated nodes. Example:
| node_1 | node_2 | node_3 | node_4 | node_5 | node_6 |
|---|---|---|---|---|---|
| redis-a1 | redis-b1 | redis-c1 | redis-b2 | redis-c2 | redis-a2 |
In this scenario, type 1 nodes are master nodes and type 2 nodes are slave nodes.
This deployment can also be reduced to 3 nodes, at a greater risk of losing data, conforming this scenario:
| node_1 | node_2 | node_3 |
|---|---|---|
| groupA | groupB | groupC |
| redis-a1 + redis-c2 | redis-b1 + redis-c2 | redis-c1 + redis-b2 |
If one the hosts becomes unavailable, the service will still be available and able to completely recover after the host is back on.
Access the Requirements section of this page to read on how to install the dependencies for the modules to run.
// In progress
Copy the file minimal/group_redis/group.yaml to redis_groupA.yaml on the host node_1.
Execute the following commands to start group A's redis-master and redis-replica.
sudo docker-compose -f redis_groupA.yaml up -dCopy the file minimal/group_redis/group.yaml to redis_groupB.yaml on the host node_2.
Execute the following commands to start group B's redis-master and redis-replica.
sudo docker-compose -f redis_groupB.yaml up -dCopy the file minimal/group_redis/group.yaml to redis_groupC.yaml on the host node_3.
Execute the following commands to start group C's redis-master and redis-replica.
sudo docker-compose -f redis_groupC.yaml up -dExecute the following command on host node_1 (and confirm).
sudo docker run -i --rm --network host --entrypoint redis-cli redis:5.0.3 --cluster create node_1:6379 node_2:6379 node_3:6379 node_1:6380 node_3:6380 node_2:6380 --cluster-replicas 1Consult logs with the following command.
sudo docker-compose -f redis_group{ID} logs -fThe term {ID} must be replaced with the node number.
Stop the service with the following command.
sudo docker-compose -f redis_group{ID} downO backup do Redis é salvo no diretório /data de cada host.