使用 docker-compose 一键部署多个 redis 实例

目录

1. 前期准备

2. 导入镜像

3. 部署redis master脚本

4. 部署redis slave脚本

5. 模板文件

6. 部署redis

7. 基本维护


1. 前期准备

新部署前可以从仓库(repository)下载 redis 镜像,或者从已有部署中的镜像生成文件:

# 查看当前本地镜像
docker images
# 生成本地镜像文件
docker save <IMAGE ID> -o redis_503.tar

2. 导入镜像

# 在新部署的机器上导入镜像
docker load -i redis_503.tar
docker images

3. 部署redis master脚本

redis-master-deploy.sh 文件内容如下:

#!/bin/bashif [ ! -n "$1" ] ;thenecho "执行方式:redis-master-deploy.sh 镜像 redis起始端口号,如 redis-master-deploy.sh a.com:8443/dockerhub/redis:5.0.3 7001"exit
fiif [ ! -n "$2" ] ;thenecho "执行方式:redis-master-deploy.sh 镜像 redis起始端口号,如 redis-master-deploy.sh a.com:8443/dockerhub/redis:5.0.3 7001"exit
fiimage=${1//\//\\/}
port=$2
len=${#port}for ((var=0; var<$len; var++))
doa=${port:$var:1}if [ $var -eq 0 ]; thensentinel_port=$(($a+1))elif [ $var -eq $(($len-1)) ]; thensentinel_port=${sentinel_port}1elsesentinel_port=${sentinel_port}0fi
done# redis-server
for i in {1..16}
doold_port=$((7000+$i))new_port=$(($port + $i -1))sed_para=$sed_para"s/${old_port}/${new_port}/g;"mkdir -p /usr/local/etc/redis/redis$i/cp -f ~/redis.conf.template /usr/local/etc/redis/redis$i/redis.confsed -i 's/7001/'"${new_port}"'/g;s/redis1/redis'"${i}"'/g;' /usr/local/etc/redis/redis$i/redis.conf
donecp -f ~/docker-compose-server.yml.template /usr/local/etc/redis/docker-compose.yml
sed -e ${sed_para} -i /usr/local/etc/redis/docker-compose.yml
sed -i 's/a.com:8443\/dockerhub\/redis:5.0.3/'"${image}"'/g;' /usr/local/etc/redis/docker-compose.yml# sentinel
mkdir -p /usr/local/etc/redis/sentinel/
cp -f ~/sentinel.conf.template /usr/local/etc/redis/sentinel/sentinel.conf
ip=`hostname -I | awk '{print $1}'`
sed -i 's/172.18.29.56/'"${ip}"'/g;s/8001/'"${sentinel_port}"'/g;' /usr/local/etc/redis/sentinel/sentinel.conf
sed -e ${sed_para} -i /usr/local/etc/redis/sentinel/sentinel.conf
cp -f ~/docker-compose-sentinel.yml.template /usr/local/etc/redis/sentinel/docker-compose.yml
sed -i 's/a.com:8443\/dockerhub\/redis:5.0.3/'"${image}"'/g;s/8001/'"${sentinel_port}"'/g;' /usr/local/etc/redis/sentinel/docker-compose.yml# start-all
chown -R polkitd:root /usr/local/etc/redis/
/usr/libexec/docker/cli-plugins/docker-compose -f /usr/local/etc/redis/docker-compose.yml up -d
/usr/libexec/docker/cli-plugins/docker-compose -f /usr/local/etc/redis/sentinel/docker-compose.yml up -d

4. 部署redis slave脚本

redis-slave-deploy.sh 文件内容如下:

#!/bin/bashif [ ! -n "$1" ] ;thenecho "执行方式:redis-master-deploy.sh 镜像 redis起始端口号 master_ip,如 redis-master-deploy.sh a.com:8443/dockerhub/redis:5.0.3 7001 172.18.29.56"exit
fiif [ ! -n "$2" ] ;thenecho "执行方式:redis-master-deploy.sh 镜像 redis起始端口号 master_ip,如 redis-master-deploy.sh a.com:8443/dockerhub/redis:5.0.3 7001 172.18.29.56"exit
fiif [ ! -n "$3" ] ;thenecho "执行方式:redis-master-deploy.sh 镜像 redis起始端口号 master_ip,如 redis-master-deploy.sh a.com:8443/dockerhub/redis:5.0.3 7001 172.18.29.56"exit
fiimage=${1//\//\\/}
port=$2
len=${#port}for ((var=0; var<$len; var++))
doa=${port:$var:1}if [ $var -eq 0 ]; thensentinel_port=$(($a+1))elif [ $var -eq $(($len-1)) ]; thensentinel_port=${sentinel_port}1elsesentinel_port=${sentinel_port}0fi
done# redis-server
for i in {1..16}
doold_port=$((7000+$i))new_port=$(($port + $i -1))sed_para=$sed_para"s/${old_port}/${new_port}/g;"mkdir -p /usr/local/etc/redis/redis$i/cp -f ~/redis.conf.template /usr/local/etc/redis/redis$i/redis.confsed -i 's/7001/'"${new_port}"'/g;s/redis1/redis'"${i}"'/g;' /usr/local/etc/redis/redis$i/redis.conf
donecp -f ~/docker-compose-server.yml.template /usr/local/etc/redis/docker-compose.yml
sed -e ${sed_para} -i /usr/local/etc/redis/docker-compose.yml
sed -i 's/a.com:8443\/dockerhub\/redis:5.0.3/'"${image}"'/g;s/172.18.29.56/'"$3"'/g;' /usr/local/etc/redis/docker-compose.yml# sentinel
mkdir -p /usr/local/etc/redis/sentinel/
cp -f ~/sentinel.conf.template /usr/local/etc/redis/sentinel/sentinel.conf
# ip=`hostname -I | awk '{print $1}'`
sed -i 's/172.18.29.56/'"$3"'/g;s/8001/'"${sentinel_port}"'/g;' /usr/local/etc/redis/sentinel/sentinel.conf
sed -e ${sed_para} -i /usr/local/etc/redis/sentinel/sentinel.conf
cp -f ~/docker-compose-sentinel.yml.template /usr/local/etc/redis/sentinel/docker-compose.yml
sed -i 's/a.com:8443\/dockerhub\/redis:5.0.3/'"${image}"'/g;s/8001/'"${sentinel_port}"'/g;' /usr/local/etc/redis/sentinel/docker-compose.yml# start-all
chown -R polkitd:root /usr/local/etc/redis/
/usr/libexec/docker/cli-plugins/docker-compose -f /usr/local/etc/redis/docker-compose.yml up -d
/usr/libexec/docker/cli-plugins/docker-compose -f /usr/local/etc/redis/sentinel/docker-compose.yml up -d

5. 模板文件

docker-compose-sentinel.yml.template 文件内容如下:

version: '3'
services:sentinel:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-sentinelports:- 8001:8001command: redis-sentinel /sentinel/sentinel.confvolumes:- /usr/local/etc/redis/sentinel/:/sentinel

docker-compose-server.yml.template 文件内容如下:

version: '3'
services:master1:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master1restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7001:7001volumes:- /usr/local/etc/redis/redis1/:/redis1command: redis-server /redis1/redis.confmaster2:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master2restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7002:7002volumes:- /usr/local/etc/redis/redis2/:/redis2command: redis-server /redis2/redis.confmaster3:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master3restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7003:7003volumes:- /usr/local/etc/redis/redis3/:/redis3command: redis-server /redis3/redis.confmaster4:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master4restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7004:7004volumes:- /usr/local/etc/redis/redis4/:/redis4command: redis-server /redis4/redis.confmaster5:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master5restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7005:7005volumes:- /usr/local/etc/redis/redis5/:/redis5command: redis-server /redis5/redis.confmaster6:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master6restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7006:7006volumes:- /usr/local/etc/redis/redis6/:/redis6command: redis-server /redis6/redis.confmaster7:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master7restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7007:7007volumes:- /usr/local/etc/redis/redis7/:/redis7command: redis-server /redis7/redis.confmaster8:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master8restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7008:7008volumes:- /usr/local/etc/redis/redis8/:/redis8command: redis-server /redis8/redis.confmaster9:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master9restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7009:7009volumes:- /usr/local/etc/redis/redis9/:/redis9command: redis-server /redis9/redis.confmaster10:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master10restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7010:7010volumes:- /usr/local/etc/redis/redis10/:/redis10command: redis-server /redis10/redis.confmaster11:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master11restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7011:7011volumes:- /usr/local/etc/redis/redis11/:/redis11command: redis-server /redis11/redis.confmaster12:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master12restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7012:7012volumes:- /usr/local/etc/redis/redis12/:/redis12command: redis-server /redis12/redis.confmaster13:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master13restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7013:7013volumes:- /usr/local/etc/redis/redis13/:/redis13command: redis-server /redis13/redis.confmaster14:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master14restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7014:7014volumes:- /usr/local/etc/redis/redis14/:/redis14command: redis-server /redis14/redis.confmaster15:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master15restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7015:7015volumes:- /usr/local/etc/redis/redis15/:/redis15command: redis-server /redis15/redis.confmaster16:image: a.com:8443/dockerhub/redis:5.0.3container_name: redis-master16restart: alwaysenvironment:- TZ=Asia/Shanghaiports:- 7016:7016volumes:- /usr/local/etc/redis/redis16/:/redis16command: redis-server /redis16/redis.conf

redis.conf.template 文件内容如下:

rename-command flushAll ""
daemonize no
port 7001
dir "/redis1"
pidfile "/redis1/redis.pid"
logfile "/redis1/redis.log"
dbfilename "dump.rdb"
save 900 1
appendonly no
appendfilename "appendonly.aof"
appendfsync always
maxmemory 500mb
maxmemory-policy volatile-lru
maxmemory-samples 3
slowlog-log-slower-than 10000
repl-backlog-size 64mb
timeout 0
repl-timeout 240requirepass "123456"
masterauth "123456"
protected-mode no

sentinel.conf.template 文件内容如下:

port 8001
protected-mode no
dir "/sentinel"sentinel monitor redis1 172.18.29.56 7001 2
sentinel auth-pass redis1 123456
sentinel down-after-milliseconds redis1 5000
sentinel failover-timeout redis1 10000sentinel monitor redis2 172.18.29.56 7002 2
sentinel auth-pass redis2 123456
sentinel down-after-milliseconds redis2 5000
sentinel failover-timeout redis2 10000sentinel monitor redis3 172.18.29.56 7003 2
sentinel auth-pass redis3 123456
sentinel down-after-milliseconds redis3 5000
sentinel failover-timeout redis3 10000sentinel monitor redis4 172.18.29.56 7004 2
sentinel auth-pass redis4 123456
sentinel down-after-milliseconds redis4 5000
sentinel failover-timeout redis4 10000sentinel monitor redis5 172.18.29.56 7005 2
sentinel auth-pass redis5 123456
sentinel down-after-milliseconds redis5 5000
sentinel failover-timeout redis5 10000sentinel monitor redis6 172.18.29.56 7006 2
sentinel auth-pass redis6 123456
sentinel down-after-milliseconds redis6 5000
sentinel failover-timeout redis6 10000sentinel monitor redis7 172.18.29.56 7007 2
sentinel auth-pass redis7 123456
sentinel down-after-milliseconds redis7 5000
sentinel failover-timeout redis7 10000sentinel monitor redis8 172.18.29.56 7008 2
sentinel auth-pass redis8 123456
sentinel down-after-milliseconds redis8 5000
sentinel failover-timeout redis8 10000sentinel monitor redis9 172.18.29.56 7009 2
sentinel auth-pass redis9 123456
sentinel down-after-milliseconds redis9 5000
sentinel failover-timeout redis9 10000sentinel monitor redis10 172.18.29.56 7010 2
sentinel auth-pass redis10 123456
sentinel down-after-milliseconds redis10 5000
sentinel failover-timeout redis10 10000sentinel monitor redis11 172.18.29.56 7011 2
sentinel auth-pass redis11 123456
sentinel down-after-milliseconds redis11 5000
sentinel failover-timeout redis11 10000sentinel monitor redis12 172.18.29.56 7012 2
sentinel auth-pass redis12 123456
sentinel down-after-milliseconds redis12 5000
sentinel failover-timeout redis12 10000sentinel monitor redis13 172.18.29.56 7013 2
sentinel auth-pass redis13 123456
sentinel down-after-milliseconds redis13 5000
sentinel failover-timeout redis13 10000sentinel monitor redis14 172.18.29.56 7014 2
sentinel auth-pass redis14 123456
sentinel down-after-milliseconds redis14 5000
sentinel failover-timeout redis14 10000sentinel monitor redis15 172.18.29.56 7015 2
sentinel auth-pass redis15 123456
sentinel down-after-milliseconds redis15 5000
sentinel failover-timeout redis15 10000sentinel monitor redis16 172.18.29.56 7016 2
sentinel auth-pass redis16 123456
sentinel down-after-milliseconds redis16 5000
sentinel failover-timeout redis16 10000

6. 部署redis

# 在 redis master 机器执行
./redis-master-deploy.sh 0f88f9be5839 20001# 在 redis slave 机器执行
./redis-slave-deploy.sh 0f88f9be5839 20001 172.18.3.15

说明:

  1. 一次创建16组redis一主两从实例
  2. 需要模板文件 /root/*.template
  3. image、port为redis-master-deploy.sh命令行参数;image、port、master_ip为redis-slave-deploy.sh命令行参数;
  4. port为16个redis-server示例的起始端口,例如:port为7001将创建 7001 - 7016 16个实例
  5. 先部署master,再部署slave,主从port参数必须相同,本例同为7001
  6. 哨兵端口位数与port参数相同,定义为:第一位为port的第一位加1,最后一位为1,中间位数为0。例如port 参数值为 20010,则哨兵端口为30001;port 参数值为 7001,则哨兵端口为8001。

7. 基本维护

# 查看镜像
docker images
# 查看容器
docker ps
# 查看容器详细信息
docker inspect <CONTAINER ID>
# 重启容器
/usr/libexec/docker/cli-plugins/docker-compose -f /usr/local/etc/redis/docker-compose.yml down
/usr/libexec/docker/cli-plugins/docker-compose -f /usr/local/etc/redis/sentinel/docker-compose.yml down
/usr/libexec/docker/cli-plugins/docker-compose -f /usr/local/etc/redis/docker-compose.yml up -d
/usr/libexec/docker/cli-plugins/docker-compose -f /usr/local/etc/redis/sentinel/docker-compose.yml up -d

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处:http://www.mzph.cn/news/16877.shtml

如若内容造成侵权/违法违规/事实不符,请联系多彩编程网进行投诉反馈email:809451989@qq.com,一经查实,立即删除!

相关文章

简单的python有趣小程序,有趣的代码大全python

这篇文章主要介绍了python简单有趣的程序源代码&#xff0c;具有一定借鉴价值&#xff0c;需要的朋友可以参考下。希望大家阅读完这篇文章后大有收获&#xff0c;下面让小编带着大家一起了解一下。

网络防御技术:防火墙与入侵检测系统

目录 简介&#xff1a; 1. 防火墙基础 1.1 类型 1.2 防火墙规则配置 2. 入侵检测系统&#xff08;IDS&#xff09;基础 2.1 类型 2.2 IDS规则配置 总结 简介&#xff1a; 在当今数字化时代&#xff0c;网络安全威胁日益增加&#xff0c;保护网络免受恶意攻击变得尤为重…

安装 mysql8.0-docker版安装

一、docker安装 安装docker2022版&#xff08;对大家有帮助&#xff09; 二、docker 安装mysql8.0 1.从 Docker Hub 下载 MySQL 8.0 镜像。打开终端并运行以下命令&#xff1a; docker pull mysql:8.0 2.创建一个 MySQL 容器并运行。在终端中运行以下命令&#xff1a; docke…

Hadoop学习日记-YARN组件

YARN(Yet Another Resource Negotiator)作为一种新的Hadoop资源管理器&#xff0c;是另一种资源协调者。 YARN是一个通用的资源管理系统和调度平台&#xff0c;可为上层应用提供统一的资源管理和调度 YARN架构图 YARN3大组件&#xff1a; &#xff08;物理层面&#xff09…

ICML 2023 | 拓展机器学习的边界

编者按&#xff1a;如今&#xff0c;机器学习已成为人类未来发展的焦点领域&#xff0c;如何进一步拓展机器学习技术和理论的边界&#xff0c;是一个极富挑战性的重要话题。7月23日至29日&#xff0c;第四十届国际机器学习大会 ICML 2023 在美国夏威夷举行。该大会是由国际机器…

HarmonyOS/OpenHarmony元服务开发-配置卡片的配置文件

卡片相关的配置文件主要包含FormExtensionAbility的配置和卡片的配置两部分&#xff1a; 1.卡片需要在module.json5配置文件中的extensionAbilities标签下&#xff0c;配置FormExtensionAbility相关信息。FormExtensionAbility需要填写metadata元信息标签&#xff0c;其中键名称…

CentOS 7安装Docker

文章目录 &#x1f31e;版本选择☀️1.CentOS安装Docker&#x1f331;1.1.卸载&#xff08;可选&#xff09;&#x1f331;1.2.安装docker&#x1f331;1.3.启动docker&#x1f331;1.4.配置镜像加速 ☀️2.CentOS7安装DockerCompose&#x1f331;2.1.下载&#x1f331;2.2.修改…

赛车游戏——【极品飞车】(内含源码inscode在线运行)

前言 「作者主页」&#xff1a;雪碧有白泡泡 「个人网站」&#xff1a;雪碧的个人网站 「推荐专栏」&#xff1a; ★java一站式服务 ★ ★前端炫酷代码分享 ★ ★ uniapp-从构建到提升★ ★ 从0到英雄&#xff0c;vue成神之路★ ★ 解决算法&#xff0c;一个专栏就够了★ ★ 架…

【Lua学习笔记】Lua进阶——Table(3) 元表

接上文 文章目录 元表__tostring__call__index__newindex运算符元方法其它元表操作 元表 Q&#xff1a;为什么要使用元表&#xff1f; A&#xff1a;在Lua中&#xff0c;常常会需要表与表之间的操作。元表中提供了一些元方法&#xff0c;通过自定义元方法可以实现想要的功能&…

掌握三个基础平面构成法则 优漫动游

1.图形重复&#xff1a;通过重复使用同一种或类似的图形元素,创造出一种有节奏、有重复感的视觉效果。这种设计手法可以使海报看起来更加统一和协调,增强视觉冲击力。 掌握三个基础平面构成法则 2.字体重复&#xff1a;通过重复使用同一种或类似的字体元素,创造出一种有序…

时间复杂度为O(n2)的三种简单排序算法

1.冒泡排序 冒泡排序只会操作相邻的两个数据。每次冒泡操作都会对相邻的两个元素进行比较&#xff0c;看是否满足大小关系要求。如果不满足就让它俩互换。一次冒泡会让至少少一个元素移动到它应该在的位置&#xff0c;重复n次&#xff0c;就完成了n个数据的排序工作。 /*** …

[Tools: Pycharm] Bug合集

1. Debug mode&#xff1a;Pycharm不显示变量值&#xff08;Unable to display frame variables&#xff09;&#xff1b;在python console中交互不输出值 选择Gevent compatible&#xff1a;File > Settings > Build, Execution, Deployment > Python Debugger >…

两种单例模式

1.单例模式分为两种,饿汉模式和懒汉模式.以下是饿汉模式: public class SingleTonHungry {private static SingleTonHungry singleTonHungry new SingleTonHungry();private SingleTonHungry() {}public static SingleTonHungry getInstance() {return singleTonHungry;} }2.…

数据包在网络中传输的过程

ref: 【先把这个视频看完了】&#xff1a;数据包的传输过程【网络常识10】_哔哩哔哩_bilibili 常识都看看 》Ref&#xff1a; 1. 这个写的嘎嘎好&#xff0c;解释了为啥4层7层5层&#xff0c;还有数据包封装的问题:数据包在网络中的传输过程详解_数据包传输_张孟浩_jay的博客…

<C++>二、 类和对象

1.面向对象和面向过程 C语言是面向过程的&#xff0c;关注的是过程&#xff0c;分析出求解问题的步骤&#xff0c; 通过函数调用逐步解决问题。 C是基于面向对象的&#xff0c;关注的是对象&#xff0c;将一件事情拆分成不同的对象&#xff0c;靠对象之间的交互完成。 2. C类 C…

2023 蓝桥杯真题B组 C/C++

https://www.dotcpp.com/oj/train/1089/ 题目 3150: 蓝桥杯2023年第十四届省赛真题-冶炼金属 题目描述 小蓝有一个神奇的炉子用于将普通金属 O 冶炼成为一种特殊金属 X。这个炉子有一个称作转换率的属性 V&#xff0c;V 是一个正整数&#xff0c;这意味着消耗 V 个普通金 属 O…

golang静态编译及编译失败排查步骤

文章目录 一、背景前提 二、静态编译概述1、执行静态编译设置CGO_ENABLED方式指定link方式 2、编译报错分析&#xff08;1&#xff09;确认系统上有没有安装libopus&#xff08;2&#xff09;设置LD_LIBRARY_PATH 三、详细排查过程1、下载bpf排查工具bcc, bcc-tools,python-bcc…

Java开发 - Redis常见问题场景及解决办法一览

前言 前面几篇博客对Redis的讲解不可谓不详细&#xff0c;从单节点到主从&#xff0c;到sentinel哨兵&#xff0c;到Redis Cluster都一一搭配使用给大家做了讲解&#xff0c;但在使用Redis的过程中我们还是要注意一些比较常见的问题&#xff0c;比如穿透、击穿等等&#xff0c…

助力保险行业数字化创新,麒麟信安参展2023中国财险科技应用高峰论坛

2023年7月27日&#xff0c;由中科软科技股份有限公司主办的“中国财险科技应用高峰论坛”在北京古北水镇成功举办。作为享誉中国保险科技界的盛会&#xff0c;本次活动以“数智保险 创新未来”主题&#xff0c;汇聚全国数百位保险公司主管领导、资深保险行业信息化专家&#xf…

Spring中解决循环依赖为什么要用三级缓存,二级为什么不行呢?

在Spring中解决循环依赖时&#xff0c;使用三级缓存是因为循环依赖的解决过程需要多个阶段的处理&#xff0c;并且需要保留中间状态。而使用二级缓存无法满足这些需求。 循环依赖是指两个或多个Bean之间相互依赖的情况&#xff0c;例如A依赖B&#xff0c;B又依赖A。为了解决循…