redis哨兵模式搭建

1、环境准备:

  1. 准备3台虚拟机 ,ip地址 192.168.20.211,192.168.20.212,192.168.20.213
  2. 安装redis

2、先配置常规主从,并启动redis

  1. 192.168.20.211 作为master,其他两个节点为slave
bash 复制代码
[root@redis01 redis]# cat /etc/redis/redis.conf
daemonize yes
bind 0.0.0.0
port 6379
requirepass 123456
save 3600 1 300 100 60 10000

dir /var/lib/redis
dbfilename dump.rdb
logfile /var/log/redis/redis.log
pidfile /var/run/redis_6379.pid

masterauth 123456

# 查看主从信息
[root@redis01 redis]# 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:master
connected_slaves:2
slave0:ip=192.168.20.212,port=6379,state=online,offset=189704,lag=1
slave1:ip=192.168.20.213,port=6379,state=online,offset=189718,lag=0
  1. 192.168.20.212
bash 复制代码
[root@redis02 redis]# cat /etc/redis/redis.conf 
daemonize yes
bind 0.0.0.0
port 6379
requirepass 123456
save 3600 1 300 100 60 10000

dir /var/lib/redis
dbfilename dump.rdb
logfile /var/log/redis/redis.log
pidfile /var/run/redis_6379.pid

replicaof 192.168.20.211 6379
masterauth 123456
  1. 192.168.20.213
bash 复制代码
[root@redis03 redis]# cat /etc/redis/redis.conf 
daemonize yes
bind 0.0.0.0
port 6379
requirepass 123456
save 3600 1 300 100 60 10000

dir /var/lib/redis
dbfilename dump.rdb
logfile /var/log/redis/redis.log
pidfile /var/run/redis_6379.pid

replicaof 192.168.20.211 6379
masterauth 123456

3、配置sentinel,启动sentinel

  1. sentinel 配置,3个节点配置一样
bash 复制代码
[root@redis01 redis]# cat sentinel.conf
daemonize yes
bind 0.0.0.0
port 26379
requirepass 123456

dir /tmp
logfile /var/log/redis/sentinel.log
pidfile /var/run/redis-sentinel.pid

sentinel monitor mymaster 192.168.20.211 6379 2
sentinel auth-pass mymaster 123456
sentinel down-after-milliseconds mymaster 30000
  1. 启动
bash 复制代码
[root@redis01 redis]#  systemctl  start redis-sentinel
  1. 查看
bash 复制代码
[root@redis01 ~]# redis-cli -p 26379
127.0.0.1:26379> auth 123456
OK
127.0.0.1:26379> INFO sentinel
# Sentinel
sentinel_masters:1
sentinel_tilt:0
sentinel_running_scripts:0
sentinel_scripts_queue_length:0
sentinel_simulate_failure_flags:0
master0:name=mymaster,status=ok,address=192.168.20.211:6379,slaves=2,sentinels=3
127.0.0.1:26379> SENTINEL GET-MASTER-ADDR-BY-NAME mymaster
1) "192.168.20.211"
2) "6379"
127.0.0.1:26379> SENTINEL MASTER mymaster
 1) "name"
 2) "mymaster"
 3) "ip"
 4) "192.168.20.211"
 5) "port"
 6) "6379"
 7) "runid"
 8) "2f978a656c264e85808b4ed796079cf588703bcf"
 9) "flags"
10) "master"
11) "link-pending-commands"
12) "0"
13) "link-refcount"
14) "1"
15) "last-ping-sent"
16) "0"
17) "last-ok-ping-reply"
18) "642"
19) "last-ping-reply"
20) "642"
21) "down-after-milliseconds"
22) "30000"
23) "info-refresh"
24) "3235"
25) "role-reported"
26) "master"
27) "role-reported-time"
28) "1238087"
29) "config-epoch"
30) "0"
31) "num-slaves"
32) "2"
33) "num-other-sentinels"
34) "2"
35) "quorum"
36) "2"
37) "failover-timeout"
38) "180000"
39) "parallel-syncs"
40) "1"
127.0.0.1:26379> SENTINEL slaves mymaster
1)  1) "name"
    2) "192.168.20.213:6379"
    3) "ip"
    4) "192.168.20.213"
    5) "port"
    6) "6379"
    7) "runid"
    8) "9f57dbe48e38707a18b30a284c9a9d34c0ec0c3c"
    9) "flags"
   10) "slave"
   11) "link-pending-commands"
   12) "0"
   13) "link-refcount"
   14) "1"
   15) "last-ping-sent"
   16) "0"
   17) "last-ok-ping-reply"
   18) "170"
   19) "last-ping-reply"
   20) "170"
   21) "down-after-milliseconds"
   22) "30000"
   23) "info-refresh"
   24) "7705"
   25) "role-reported"
   26) "slave"
   27) "role-reported-time"
   28) "1975580"
   29) "master-link-down-time"
   30) "0"
   31) "master-link-status"
   32) "ok"
   33) "master-host"
   34) "192.168.20.211"
   35) "master-port"
   36) "6379"
   37) "slave-priority"
   38) "100"
   39) "slave-repl-offset"
   40) "520092"
   41) "replica-announced"
   42) "1"
2)  1) "name"
    2) "192.168.20.212:6379"
    3) "ip"
    4) "192.168.20.212"
    5) "port"
    6) "6379"
    7) "runid"
    8) "acbaff90d00b240e8dd5ac6132a99bfa5c357c62"
    9) "flags"
   10) "slave"
   11) "link-pending-commands"
   12) "0"
   13) "link-refcount"
   14) "1"
   15) "last-ping-sent"
   16) "0"
   17) "last-ok-ping-reply"
   18) "170"
   19) "last-ping-reply"
   20) "170"
   21) "down-after-milliseconds"
   22) "30000"
   23) "info-refresh"
   24) "7705"
   25) "role-reported"
   26) "slave"
   27) "role-reported-time"
   28) "1975592"
   29) "master-link-down-time"
   30) "0"
   31) "master-link-status"
   32) "ok"
   33) "master-host"
   34) "192.168.20.211"
   35) "master-port"
   36) "6379"
   37) "slave-priority"
   38) "100"
   39) "slave-repl-offset"
   40) "520092"
   41) "replica-announced"
   42) "1"

4 验证

停掉主节点的,看是否会把从节点提升成主节点

bash 复制代码
[root@redis02 redis]# redis-cli  -p 26379
127.0.0.1:26379> info sentinel
NOAUTH Authentication required.
127.0.0.1:26379> auth 123456
OK
127.0.0.1:26379> info sentinel
# Sentinel
sentinel_masters:1
sentinel_tilt:0
sentinel_running_scripts:0
sentinel_scripts_queue_length:0
sentinel_simulate_failure_flags:0
master0:name=mymaster,status=ok,address=192.168.20.213:6379,slaves=2,sentinels=3
相关推荐
bksczm15 小时前
Redis Cluster 分片集群详解:槽路由、故障判定与扩缩容
数据库·redis·分布式
黑十17 小时前
FDE 怎么快速搭一个可演示页面?最小前端方案
java·大数据·前端·数据库·人工智能
Databend18 小时前
OpenRaft 自定义 Membership,按部署拓扑选择 Quorum
大数据·数据库·数据分析
Databend18 小时前
用 SQL 排查支付故障,OpenTelemetry 接入 Databend Cloud 实战
大数据·数据库·sql
kyle~18 小时前
SQLite -- 低成本持久化能力
数据库·sqlite
上海潭龙东海科技有限公司18 小时前
智慧堆场动态模型三维实时孪生重构智能管控
大数据·网络·数据库·算法·重构
老纪的技术唠嗑局19 小时前
OceanBase AI数据大会,我会这么逛
数据库
星恒随风19 小时前
MySQL 从零入门(九):事务管理详解——ACID、COMMIT、ROLLBACK、SAVEPOINT 与四种隔离级别
linux·服务器·数据库·笔记·mysql
草莓熊Lotso19 小时前
【C++ 基于微服务的即时通讯系统】ElasticSearch 用户数据管理实现
linux·数据库·c++·elasticsearch·微服务·架构