文章目录

  • 一、前置准备
    • 启动redis服务
    • 启动sentinel服务
    • 查看sentiel启动日志
  • 二、实战故障转移
    • 2.1. 主节点停止
    • 2.2. Sentienl监控日志
    • 2.3. 节点信息监控
    • 2.4. 故障转移后变化
    • 2.5. 重新启动
    • 2.6. sentine日志
    • 2.7. 节点信息监控
    • 2.8. 配置文件变化
    • 2.9. 读写验证
一、前置准备
启动redis服务
# 查看redis进程
ps -ef |grep redis# 启动redis服务
/usr/local/redis/bin/redis-server /usr/local/redis/conf/redis.conf#查看主从节点信息
/usr/local/redis/bin/redis-cli -a 123456
info replication
启动sentinel服务

声明:在启动3个redis服务的前提下,再依次启动3个sentinel服务

/usr/local/redis/bin/redis-sentinel /usr/local/redis/conf/sentiel.conf
查看sentiel启动日志
tail -f /usr/local/redis/log/sentinel.log
二、实战故障转移
2.1. 主节点停止
[root@bigdata01 redis-6.2.0]# /usr/local/redis/bin/redis-cli -a 123456
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6379> info replcation
127.0.0.1:6379> info replication
# Replication
role:master
connected_slaves:2
slave0:ip=xxx.xxx.92.101,port=6379,state=online,offset=3xxx,lag=1
slave1:ip=xxx.xxx.92.102,port=6379,state=online,offset=3xxx,lag=1
master_failover_state:no-failover
master_replid:4f07bacde969998356194ad698c6dd7e2f6f7da2
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:3xxx
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1391
repl_backlog_histlen:1778
127.0.0.1:6379> SHUTDOWN
not connected>
2.2. Sentienl监控日志

mymaster 主节点 xxx.xxx.92.100 6379 被添加主观下线标记,其他的sentinel每秒一次和xxx.xxx.92.100 6379的通信
# +sdown master mymaster xxx.xxx.92.100 6379
启动一个新选举流程,记录当前选举的次数
# +new-epoch 1
投票选举一个sentinel去做故障转移这件事
# +vote-for-leader a20913bfcbeb3a5d8d58ce1bd372cc40455xxx10 1
客观下线:当前环境内多个sentinel节点对我们的某一个服务器标记为主观下线,满足quorum 仲裁的选项值之后,标记为客观下线
# +odown master mymaster xxx.xxx.92.100 6379 #quorum 3/2
# Next failover delay: I will not start a failover before Sun Jul  4 22:39:56 2021
# +config-update-from sentinel a20913bfcbeb3a5d8d58ce1bd372cc40455xxx10 xxx.xxx.92.1026379
# +switch-master mymaster xxx.xxx.92.100 6379 xxx.xxx.92.101 6379
* +slave slave xxx.xxx.92.102:6379 xxx.xxx.92.102 6379 @ mymaster xxx.xxx.92.101 6379
* +slave slave xxx.xxx.92.100:6379 xxx.xxx.92.100 6379 @ mymaster xxx.xxx.92.101 6379
# +sdown slave xxx.xxx.92.100:6379 xxx.xxx.92.100 6379 @ mymaster xxx.xxx.92.101 6379
2.3. 节点信息监控

查看故障转移后的节点信息
01节点信息

[root@bigdata02 ~]# /usr/local/redis/bin/redis-cli -a 123456
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6379> info replication
# Replication
role:slave
master_host:xxx.xxx.92.100
master_port:6379
master_link_status:up
master_last_io_seconds_ago:6
master_sync_in_progress:0
slave_repl_offset:3196
slave_priority:100
slave_read_only:1
connected_slaves:0
master_failover_state:no-failover
master_replid:4f07bacde969998356194ad698c6dd7e2f6f7da2
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:3196
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1391
repl_backlog_histlen:1806# 故障转移后 -------------------------------------------------------------------
127.0.0.1:6379> info replication
# Replication
role:master
connected_slaves:1
slave0:ip=xxx.xxx.92.102,port=6379,state=online,offset=380674,lag=1
master_failover_state:no-failover
master_replid:424069affa171e62af3e2c65a2ee1cb27ecb6c2f
master_replid2:4f07bacde969998356194ad698c6dd7e2f6f7da2
master_repl_offset:380674
second_repl_offset:156702
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1391
repl_backlog_histlen:379284
127.0.0.1:6379> 

02节点信息

[root@bigdata03 ~]# /usr/local/redis/bin/redis-cli -a 123456
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6379> info replication
# Replication
role:slave
master_host:xxx.xxx.92.100
master_port:6379
master_link_status:up
master_last_io_seconds_ago:4
master_sync_in_progress:0
slave_repl_offset:3210
slave_priority:100
slave_read_only:1
connected_slaves:0
master_failover_state:no-failover
master_replid:4f07bacde969998356194ad698c6dd7e2f6f7da2
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:3210
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1433
repl_backlog_histlen:1778# 故障转移后 -------------------------------------------------------------------
127.0.0.1:6379> info replication
# Replication
role:slave
master_host:xxx.xxx.92.101
master_port:6379
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:381546
slave_priority:100
slave_read_only:1
connected_slaves:0
master_failover_state:no-failover
master_replid:424069affa171e62af3e2c65a2ee1cb27ecb6c2f
master_replid2:4f07bacde969998356194ad698c6dd7e2f6f7da2
master_repl_offset:381546
second_repl_offset:156702
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1433
repl_backlog_histlen:380114
127.0.0.1:6379> 
2.4. 故障转移后变化

01节点由slave节点变成了master节点,02仍然后slave节点

2.5. 重新启动

故障的 100节点(原主节点)重新启动

/usr/local/redis/bin/redis-server /usr/local/redis/conf/redis.conf
2.6. sentine日志
* +convert-to-slave slave xxx.xxx.92.100:6379 xxx.xxx.92.100 6379 @ mymaster xxx.xxx.92.101 6379
2.7. 节点信息监控
[root@bigdata01 redis-6.2.0]# /usr/local/redis/bin/redis-cli -a 123456
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6379> info replication
# Replication
role:slave
master_host:xxx.xxx.92.101
master_port:6379
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:528510
slave_priority:100
slave_read_only:1
connected_slaves:0
master_failover_state:no-failover
master_replid:424069affa171e62af3e2c65a2ee1cb27ecb6c2f
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:528510
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:518136
repl_backlog_histlen:10375
127.0.0.1:6379>

01节点信息

[root@bigdata02 ~]# /usr/local/redis/bin/redis-cli -a 123456
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6379> info replication
# Replication
role:slave
master_host:xxx.xxx.92.100
master_port:6379
master_link_status:up
master_last_io_seconds_ago:6
master_sync_in_progress:0
slave_repl_offset:3196
slave_priority:100
slave_read_only:1
connected_slaves:0
master_failover_state:no-failover
master_replid:4f07bacde969998356194ad698c6dd7e2f6f7da2
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:3196
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1391
repl_backlog_histlen:1806# 故障转移后 -------------------------------------------------------------------
127.0.0.1:6379> info replication
# Replication
role:master
connected_slaves:1
slave0:ip=xxx.xxx.92.102,port=6379,state=online,offset=380674,lag=1
master_failover_state:no-failover
master_replid:424069affa171e62af3e2c65a2ee1cb27ecb6c2f
master_replid2:4f07bacde969998356194ad698c6dd7e2f6f7da2
master_repl_offset:380674
second_repl_offset:156702
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1391
repl_backlog_histlen:379284#原主节点重新启动后 -------------------------------------------------------------------
127.0.0.1:6379> info replication
# Replication
role:master
connected_slaves:2
slave0:ip=xxx.xxx.92.102,port=6379,state=online,offset=537589,lag=1
slave1:ip=xxx.xxx.92.100,port=6379,state=online,offset=537732,lag=0
master_failover_state:no-failover
master_replid:424069affa171e62af3e2c65a2ee1cb27ecb6c2f
master_replid2:4f07bacde969998356194ad698c6dd7e2f6f7da2
master_repl_offset:537875
second_repl_offset:156702
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1391
repl_backlog_histlen:536485
127.0.0.1:6379>

02节点信息

[root@bigdata03 ~]# /usr/local/redis/bin/redis-cli -a 123456
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6379> info replication
# Replication
role:slave
master_host:xxx.xxx.92.100
master_port:6379
master_link_status:up
master_last_io_seconds_ago:4
master_sync_in_progress:0
slave_repl_offset:3210
slave_priority:100
slave_read_only:1
connected_slaves:0
master_failover_state:no-failover
master_replid:4f07bacde969998356194ad698c6dd7e2f6f7da2
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:3210
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1433
repl_backlog_histlen:1778# 故障转移后 -------------------------------------------------------------------
127.0.0.1:6379> info replication
# Replication
role:slave
master_host:xxx.xxx.92.101
master_port:6379
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:381546
slave_priority:100
slave_read_only:1
connected_slaves:0
master_failover_state:no-failover
master_replid:424069affa171e62af3e2c65a2ee1cb27ecb6c2f
master_replid2:4f07bacde969998356194ad698c6dd7e2f6f7da2
master_repl_offset:381546
second_repl_offset:156702
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1433
repl_backlog_histlen:380114#原主节点重新启动后 -------------------------------------------------------------------
127.0.0.1:6379> info replication
# Replication
role:slave
master_host:xxx.xxx.92.101
master_port:6379
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:556005
slave_priority:100
slave_read_only:1
connected_slaves:0
master_failover_state:no-failover
master_replid:424069affa171e62af3e2c65a2ee1cb27ecb6c2f
master_replid2:4f07bacde969998356194ad698c6dd7e2f6f7da2
master_repl_offset:556005
second_repl_offset:156702
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1433
repl_backlog_histlen:554573
127.0.0.1:6379>
2.8. 配置文件变化

原100主节点

# 放行访问IP的限制 多个用空格隔开
# 0.0.0.0 代表无限制
bind 0.0.0.0# 后台启动开启
daemonize yes# 日志存储目录以及日志文件名
logfile "/usr/local/redis/log/redis.log"# rdb数据文件名
dbfilename "dump.rdb"# aof模式开启
appendonly no# aof数据文件名
appendfilename "appendonly.aof"#rdb数据文件和aof数据文件存储目录
dir "/usr/local/redis/data"# 设置密码
requirepass 123456# 从节点访问主节点的密码(必须和requirepass 一致)
masterauth "123456"#从节点只读模式
replica-read-only yes
# Generated by CONFIG REWRITE
pidfile "/var/run/redis.pid"
save 3600 1
save 300 100
save 60 10000
user default on #8d969eef6ecad3c29a3a629280e686cf0c3f5d5a86aff3ca12020c923adc6c92 ~* &* +@all
replicaof xxx.xxx.92.101 6379

变化:最下面添加了主节点信息

原01节点

# 放行访问IP的限制 多个用空格隔开
# 0.0.0.0 代表无限制
bind 0.0.0.0# 后台启动开启
daemonize yes# 日志存储目录以及日志文件名
logfile "/usr/local/redis/log/redis.log"# rdb数据文件名
dbfilename "dump.rdb"# aof模式开启
appendonly no# aof数据文件名
appendfilename "appendonly.aof"#rdb数据文件和aof数据文件存储目录
dir "/usr/local/redis/data"# 设置密码
requirepass 123456# 从节点访问主节点的密码(必须和requirepass 一致)
masterauth "123456"#从节点只读模式
replica-read-only yes# 从节点从属于那个主节点# Generated by CONFIG REWRITE
pidfile "/var/run/redis.pid"
save 3600 1
save 300 100
save 60 10000
user default on #8d969eef6ecad3c29a3a629280e686cf0c3f5d5a86aff3ca12020c923adc6c92 ~* &* +@all

变化:原来配置的主节点信息没了

02节点信息

# 放行访问IP的限制 多个用空格隔开
# 0.0.0.0 代表无限制
bind 0.0.0.0# 后台启动开启
daemonize yes# 日志存储目录以及日志文件名
logfile "/usr/local/redis/log/redis.log"# rdb数据文件名
dbfilename "dump.rdb"# aof模式开启
appendonly no# aof数据文件名
appendfilename "appendonly.aof"#rdb数据文件和aof数据文件存储目录
dir "/usr/local/redis/data"# 设置密码
requirepass 123456# 从节点访问主节点的密码(必须和requirepass 一致)
masterauth "123456"#从节点只读模式
replica-read-only yes# 从节点从属于那个主节点
replicaof xxx.xxx.92.101 6379
# Generated by CONFIG REWRITE
pidfile "/var/run/redis.pid"
save 3600 1
save 300 100
save 60 10000
user default on #8d969eef6ecad3c29a3a629280e686cf0c3f5d5a86aff3ca12020c923adc6c92 ~* &* +@all
2.9. 读写验证
# 登陆redis客户端
/usr/local/redis/bin/redis-cli --user default --pass 123456
#故障转移后的100机器现在为slave节点,可读不可写
[root@bigdata01 redis-6.2.0]# /usr/local/redis/bin/redis-cli --user default --pass 123456
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6379> set name lisi
(error) READONLY You can't write against a read only replica.
127.0.0.1:6379>
#故障转移后的101机器现在为master节点,可以读写
[root@bigdata02 ~]# /usr/local/redis/bin/redis-cli --user default --pass 123456
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6379> set name lisi
OK
127.0.0.1:6379> get name
"lisi"
127.0.0.1:6379> 
#故障转移后的102机器现在为slave节点,可读不可写
[root@bigdata03 ~]# /usr/local/redis/bin/redis-cli --user default --pass 123456
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6379> set name wangwu
(error) READONLY You can't write against a read only replica.
127.0.0.1:6379> get name
"lisi"
127.0.0.1:6379>

(进阶篇)Redis6.2.0 集群 哨兵模式_故障转移_03相关推荐

  1. (进阶篇)Redis6.2.0 集群 哨兵模式_搭建_01

    文章目录 一.概念架构简述 1. Redis Sentinel简述 2. Redis Sentinel优点 3. Redis Sentinel缺点 二.哨兵搭建实现 2.1. 编写配置文件 2.2. ...

  2. (进阶篇)Redis6.2.0 集群 哨兵模式_哨兵工作原理_02

    文章目录 1. 主从复制哨兵架构图 2. 定时任务 3. 主观下线 4. 客观下线 5. 仲裁 6. 哨兵工作原理 1. 主从复制哨兵架构图 2. 定时任务 Sentinel内部有3个定时任务分别是: ...

  3. 腾讯云~Redis6.2.6 伪集群 哨兵模式_搭建

    文章目录 一.redis准备3节点 1. 创建目录 2. 节点1~配置 3. 节点2~配置 4. 节点3~配置 5. 启动redis 二.新增sentinel配置 1. sentinel_01.con ...

  4. Redis高可用集群-哨兵模式(Redis-Sentinel)搭建配置教程【Windows环境】

    ================================================= 人工智能教程.零基础!通俗易懂!风趣幽默!大家可以看看是否对自己有帮助! 点击查看高清无码教程 == ...

  5. Redis集群-哨兵模式

    版权声明:本文为博主原创文章,未经博主允许不得转载. https://blog.csdn.net/liuzhixiong_521/article/details/84797609 文章目录 概述    ...

  6. 消息队列专题(架构篇):RabbitMQ 的集群架构模式

    RabbitMQ 的集群架构模式主要有四种,分别是主备模式.远程模式.多活模式和镜像模式,本篇博客将依次介绍这四种架构模式,其中的镜像模式使用范围最广,我们将对其进行重点介绍. 主备模式 主备模式是指 ...

  7. (进阶篇)Redis6.2.0 集群 主从复制_原理剖析_02

    文章目录 一.主从复制流程 1. 主从复制流程图 2. 主从复制日志 二.主从复制信息剖析 2.1. 主节点信息剖析 2.2. 从节点信息剖析 三.关键术语 3.1. 复制功能开启 3.2. 全量复制 ...

  8. (进阶篇)Redis6.2.0 集群 主从复制_搭建_01

    文章目录 1. 部署划分 2. 单机安装Redis 3. 创建配置/数据/日志目录 4. 修改配置文件 5. redis启动 6. 登录查看信息 7. 读写分离 1. 部署划分 ip 角色 192.1 ...

  9. down redis集群_Redis总结(十)redis集群-哨兵模式

    模式二:哨兵模式 上一篇问讲述了redis集群的主从模式,这一篇我们讲述哨兵模式. Redis 的 Sentinel 系统用于管理多个 Redis 服务器(instance), 该系统执行以下三个任务 ...

最新文章

  1. (0095)iOS开发之本地文件预览的三种方法(3)
  2. python导入csv文件-python读写csv文件
  3. java的两种运行机制_Java☞JVM工作原理
  4. 【OpenCV3】视频读写——cv::VideoCapture和cv::VideoWriter详解
  5. SyntaxError: Missing parentheses in call to 'print'
  6. Oracle集合查询
  7. 3.14圆周率节,这5本书带你领略数学的魅力
  8. web服务器压力测试工具
  9. ELASTIC-PHP + IK分词器 + THINKPHP6 初次使用 (关键词查询)
  10. 大学毕业生,关于转正定级和干部身份你懂吗?
  11. wkwebview 预览文件_iOS之H5调用系统相册相机浏览文件
  12. win10开始菜单没有反应
  13. 如何在EverEdit编辑器中一键编译运行JAVA并接收键盘输入数据
  14. bilibili 哔哩哔哩 2018秋招试题
  15. Idea控制台 CMD Tomcat乱码
  16. 使用Weevely工具上传一句话木马
  17. NIST随机数测试软件下载,安装、和使用,分析方法最新版(19年4月)
  18. MySQL数据库——约束
  19. 云原生|kubernetes|集群网络优化之启用ipvs
  20. jmeter-跨线程组调用token

热门文章

  1. 如何摇晃一瓶水使其核聚变?
  2. 从平庸到杰出,技术人应该专注的底层知识是什么?
  3. 判别模型、生成模型与朴素贝叶斯方法
  4. 人工智能技术将重塑银行业
  5. java编码规范右大括号换行_java编码规范摘选
  6. 解密 云HBase 冷热分离技术原理
  7. 阿里云异构计算产品是如何保障双11业务的
  8. 杭州云栖大会阿里云放大招,8K远程医疗会诊引关注
  9. 机器学习从业人员到底做什么?
  10. 如何利用秒级监控进行mongodb故障排查