Shulou(Shulou.com)06/01 Report--

This article mainly introduces "Redis how to upgrade to containerized Redis-Sentinel cluster". In daily operation, I believe many people have doubts about how to upgrade Redis to containerized Redis-Sentinel cluster. Xiaobian consulted various materials and sorted out simple and easy operation methods. I hope to help you answer the doubts of "Redis how to upgrade to containerized Redis-Sentinel cluster"! Next, please follow the small series to learn together!

Upgrade idea: Docker-compose Redis high-availability sentinel cluster, where Redis-Sentinel containers are connected to the existing Docker Swarm overlay network to avoid confusion caused by Redis ClientApp accessing Redis-Sentinel of different networks (due to NAT translation and Port mapping). Quickly launch Redis Sentinel clusters using existing Redis dump.rdb persistence files on hosts

(1 master:2slave:3 sentinel) Modify the Redis connection string of receiver and app. Verify that the existing application is in the Docker Swarm Overlay network. By default, no other containers are allowed to be attached. Here, we need to configure the Overlay network to be attachable to facilitate Redis-Sentinel access to the network. All containers are on the same network. For deployment convenience, you can assign a fixed IP to the sentinel container....

//The overlay network name generated below is: eqidstack_webnet

networks:

webnet:

driver: overlay

attachable: true //Configure the existing overlay network as: add-on containers

.....

The official Redis mirror persistent data is stored in: /data, where we need to plug the existing host Redis dump.rdb file into the Master container.# Here is the master/slave docker-compose.yml file

version: '3.7'

services:

master:

image: redis

container_name: redis-master

command: redis-server --requirepass zxcde@1 --masterauth zxcde@1

volumes:

- /home/redis-sentinel/redis/data:/data

ports:

- "6380:6379"

networks:

- webnet

slave1:

image: redis

container_name: redis-slave-1

ports:

- "6381:6379"

command: redis-server --slaveof redis-master 6379 --masterauth zxcde@1 --requirepass zxcde@1

networks:

- webnet

slave2:

image: redis

container_name: redis-slave-2

ports:

- "6382:6379"

command: redis-server --slaveof redis-master 6379 --masterauth zxcde@1 --requirepass zxcde@1

networks:

- webnet

networks:

webnet:

external: true

name: eqidstack_webnet //Use existing Dokcer Overlay network

It has been verified that the latest version of StackExchange.Redis 2.1.58 supports Redis-sentinel in a more concise way: just change the original point-connection string, where 10.0.7.41:26379, 10.0.7.42: 26379, 10.0.7.43:26379 are sentinel container endpoints and serviceName is the Maser/slave name of the Sentinel configuration. "redis":"10.0.7.41:26379,10.0.7.42:26379,10.0.7.43:26379,serviceName=mymaster1,password=zxcde@1,abortConnect=false,connectTimeout=10000,writeBuffer=40960" At this point, the study on "How to upgrade Redis to containerized Redis-Sentinel cluster" is over, hoping to solve everyone's doubts. Theory and practice can better match to help everyone learn, go and try it! If you want to continue learning more relevant knowledge, please continue to pay attention to the website, Xiaobian will continue to strive to bring more practical articles for everyone!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.