Implementation of master-slave replication in docker compose deployment

#################################### REPLICATION ####################################

# [Slave] Configuration of connecting to Master # slaveof 172.25.0.101 6379

# 【Slave】Read-only mode# slave-read-only yes

# 【Slave】Password# masterauth <master-password>

# [Slave] Is it allowed to respond to queries during replication? Dirty data may be returned. # slave-serve-stale-data yes

# [Slave] The priority of a slave to be promoted to a master. This is only effective in sentinel mode. # slave-priority 100

# 【Slave】Slave's own IP reported to the Master
# slave-announce-ip 5.5.5.5

# 【Slave】Slave's own port reported to the Master# slave-announce-port 1234

# 【Slave】The interval between Slave pinging Master# repl-ping-slave-period 10

# 【Master/Slave】Timeout# repl-timeout 60

# [Master] Diskless means directly writing the RDB file to be copied to the Socket without storing it on the disk first repl-diskless-sync no

# [Master] If Diskless is enabled, it will wait for the specified number of seconds before replicating, so that more clients can connect within the window period and transmit in parallel. # repl-diskless-sync-delay 5

# [Master] Whether to enable the Nagle algorithm, which can reduce traffic usage but will make synchronization slower repl-disable-tcp-nodelay no

# [Master] The size of the ring buffer log, which is used to reconnect after the Slave is disconnected to avoid full replication. The default value is 1mb
# repl-backlog-size 1mb

# 【Master】When the Master disconnects all Slaves for a specified period of time, the Master will clear the backlog
# repl-backlog-ttl 3600

# [Master] When the number of slave connections is less than the specified number, the Master rejects all write operations # min-slaves-to-write 3

# [Master] When the delay is higher than the specified number of seconds, the Master rejects all write operations # min-slaves-max-lag 10

replication/
├── docker-compose.yml
├── master
│ ├── data
│ └── redis.conf
├── slave1
│ ├── data
│ └── redis.conf
└── slave2
    ├── data
    └── redis.conf

version: "3"

networks:
  redis-replication:
    driver: bridge
    ipam:
      config:
        - subnet: 172.25.0.0/24

services:
  master:
    image: redis
    container_name: redis-master
    ports:
      - "6371:6379"
    volumes:
      - "./master/redis.conf:/etc/redis.conf"
      - "./master/data:/data"
    command: ["redis-server", "/etc/redis.conf"]
    restart: always
    networks:
      redis-replication:
        ipv4_address: 172.25.0.101

  slave1:
    image: redis
    container_name: redis-slave-1
    ports:
      - "6372:6379"
    volumes:
      - "./slave1/redis.conf:/etc/redis.conf"
      - "./slave1/data:/data"
    command: ["redis-server", "/etc/redis.conf"]
    restart: always
    networks:
      redis-replication:
        ipv4_address: 172.25.0.102

  slave2:
    image: redis
    container_name: redis-slave-2
    ports:
      - "6373:6379"
    volumes:
      - "./slave2/redis.conf:/etc/redis.conf"
      - "./slave2/data:/data"
    command: ["redis-server", "/etc/redis.conf"]
    restart: always
    networks:
      redis-replication:
        ipv4_address: 172.25.0.103

port 6379
protected-mode no

repl-diskless-sync no
repl-disable-tcp-nodelay no

port 6379
protected-mode no

slaveof 172.25.0.101 6379
slave-read-only yes
slave-serve-stale-data yes

ocker-compose up -d
Creating network "replication_redis-replication" with driver "bridge"
Creating redis-slave-1 ... done
Creating redis-master ... done
Creating redis-slave-2 ... done

127.0.0.1:6371> set hello world
OK

127.0.0.1:6372> get hello
"world"

127.0.0.1:6372> set hello redis
(error) READONLY You can't write against a read only replica.