docker compose部署主從復制的實現
受限於 Redis 單點性能,加上我們對數據天生就有的備份的需求,因此 Redis 提供瞭主從復制的服務。
本文記錄瞭通過 docker compose 搭建一主雙從的 Redis 服務。
配置解析
################################# REPLICATION ################################# # 【Slave】連接 Master 的配置 # slaveof 172.25.0.101 6379 # 【Slave】隻讀模式 # slave-read-only yes # 【Slave】密碼 # masterauth <master-password> # 【Slave】復制期間是否允許響應查詢,可能會返回臟數據 # slave-serve-stale-data yes # 【Slave】Slave 晉級為 Master 的優先級,僅哨兵模式下生效 # slave-priority 100 # 【Slave】Slave 向 Master 報告的自己的 IP # slave-announce-ip 5.5.5.5 # 【Slave】Slave 向 Master 報告的自己的端口 # slave-announce-port 1234 # 【Slave】Slave ping Master 的時間間隔 # repl-ping-slave-period 10 # 【Master/Slave】超時時間 # repl-timeout 60 # 【Master】Diskless 就是直接將要復制的 RDB 文件寫入到 Socket 中,而不會先存儲到磁盤上 repl-diskless-sync no # 【Master】若開啟 Diskless,會等待指定秒之後再進行復制,以便讓更多客戶端可以在窗口期內連接,並行傳送 # repl-diskless-sync-delay 5 # 【Master】是否開啟 Nagle 算法,可以減少流量占用,但會同步得慢些 repl-disable-tcp-nodelay no # 【Master】環形緩沖日志的大小,給 Slave 斷開之後重連使用,避免全量復制,默認 1mb # repl-backlog-size 1mb # 【Master】當 Master 斷連所有 Slave 指定時間後,Master 會清空 backlog # repl-backlog-ttl 3600 # 【Master】當低於指定個 Slave 連接時,Master 拒絕所有寫操作 # min-slaves-to-write 3 # 【Master】當延遲高於指定秒數時,Master 拒絕所有寫操作 # min-slaves-max-lag 10
服務搭建
目錄結構
replication/ ├── docker-compose.yml ├── master │ ├── data │ └── redis.conf ├── slave1 │ ├── data │ └── redis.conf └── slave2 ├── data └── redis.conf
Compose File
定義瞭一個子網,方便操作,對外暴露 6371(Master)、6372、6373 端口。
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
實例配置
Master:
基本不用配置,最簡單的是指定一個端口就好瞭。
port 6379 protected-mode no repl-diskless-sync no repl-disable-tcp-nodelay no
Slave:
實例的配置保持一致就可以瞭,因為定義瞭子網,不存在端口沖突。
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
查看 Master 日志,可以看到接受瞭兩個 Slave 的復制請求:
1:M 18 Aug 2021 15:50:31.772 * Replica 172.25.0.102:6379 asks for synchronization
1:M 18 Aug 2021 15:50:31.772 * Full resync requested by replica 172.25.0.102:6379
1:M 18 Aug 2021 15:50:31.772 * Replication backlog created, my new replication IDs are ‘5d27746f14ee9be9694d794f96de6ba14a669dd1’ and ‘0000000000000000000000000000000000000000’
1:M 18 Aug 2021 15:50:31.772 * Starting BGSAVE for SYNC with target: disk
1:M 18 Aug 2021 15:50:31.773 * Background saving started by pid 19
19:C 18 Aug 2021 15:50:31.777 * DB saved on disk
19:C 18 Aug 2021 15:50:31.777 * RDB: 0 MB of memory used by copy-on-write
1:M 18 Aug 2021 15:50:31.822 * Background saving terminated with success
1:M 18 Aug 2021 15:50:31.823 * Synchronization with replica 172.25.0.102:6379 succeeded
1:M 18 Aug 2021 15:50:32.170 * Replica 172.25.0.103:6379 asks for synchronization
1:M 18 Aug 2021 15:50:32.170 * Full resync requested by replica 172.25.0.103:6379
1:M 18 Aug 2021 15:50:32.170 * Starting BGSAVE for SYNC with target: disk
1:M 18 Aug 2021 15:50:32.171 * Background saving started by pid 20
20:C 18 Aug 2021 15:50:32.175 * DB saved on disk
20:C 18 Aug 2021 15:50:32.175 * RDB: 0 MB of memory used by copy-on-write
1:M 18 Aug 2021 15:50:32.225 * Background saving terminated with success
1:M 18 Aug 2021 15:50:32.226 * Synchronization with replica 172.25.0.103:6379 succeeded
查看 Slave 日志,可以看到連接建立的全過程:
1:S 18 Aug 2021 15:50:31.771 * Connecting to MASTER 172.25.0.101:6379
1:S 18 Aug 2021 15:50:31.771 * MASTER <-> REPLICA sync started
1:S 18 Aug 2021 15:50:31.771 * Non blocking connect for SYNC fired the event.
1:S 18 Aug 2021 15:50:31.771 * Master replied to PING, replication can continue…
1:S 18 Aug 2021 15:50:31.772 * Partial resynchronization not possible (no cached master)
1:S 18 Aug 2021 15:50:31.773 * Full resync from master: 5d27746f14ee9be9694d794f96de6ba14a669dd1:0
1:S 18 Aug 2021 15:50:31.823 * MASTER <-> REPLICA sync: receiving 175 bytes from master to disk
1:S 18 Aug 2021 15:50:31.823 * MASTER <-> REPLICA sync: Flushing old data
1:S 18 Aug 2021 15:50:31.823 * MASTER <-> REPLICA sync: Loading DB in memory
1:S 18 Aug 2021 15:50:31.828 * Loading RDB produced by version 6.2.5
1:S 18 Aug 2021 15:50:31.828 * RDB age 0 seconds
1:S 18 Aug 2021 15:50:31.828 * RDB memory usage when created 1.83 Mb
1:S 18 Aug 2021 15:50:31.829 * MASTER <-> REPLICA sync: Finished with success
測試
登錄 Master,嘗試寫入新 Key。
127.0.0.1:6371> set hello world OK
登錄 Slave,查看能否讀取到:
127.0.0.1:6372> get hello "world"
Slave 嘗試寫操作:
127.0.0.1:6372> set hello redis (error) READONLY You can't write against a read only replica.
到此這篇關於docker compose部署主從復制的實現的文章就介紹到這瞭,更多相關docker compose 主從復制內容請搜索WalkonNet以前的文章或繼續瀏覽下面的相關文章希望大傢以後多多支持WalkonNet!
推薦閱讀:
- Redis主從配置和底層實現原理解析(實戰記錄)
- Redis實現主從復制方式(Master&Slave)
- 關於Redis的主從復制及哨兵問題
- 一文掌握Redis的三種集群方案(小結)
- Redis和數據庫 數據同步問題的解決