redis6.2.5 sentinel集群 + keepalived 主从自动切换和高可用

最新推荐文章于 2024-08-30 09:16:50 发布
最新推荐文章于 2024-08-30 09:16:50 发布
阅读量363 收藏 2
点赞数
文章标签： 数据库 redis
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_25934401/article/details/119955238
版权
本文详细介绍了如何在三台服务器上部署高可用的Redis集群，包括安装Redis、配置主从复制、设置哨兵(Sentinel)监控以及通过Keepalived实现VIP漂移。在配置过程中，每台服务器的角色、端口分配以及配置文件内容被详细列出。通过Keepalived的配置，确保了在主节点故障时，VIP能够自动切换到新的主节点，保证服务的连续性。
摘要由CSDN通过智能技术生成

环境

ip服务端口
100.200.100.111redis redis-sentinel6379 26379
100.200.100.112redis redis-sentinel6379 26379
100.200.100.113redis redis-sentinel6379 26379

下载安装redis

yum install -y  gcc-c++ make tcl
wget http://download.redis.io/releases/redis-6.2.5.tar.gz
tar –zxvf redis-6.2.5.tar.gz
cd redis-6.2.5
make

部署redis

操作3台机器
100.200.100.111：

[root@JUMPSER-100-200-100-111 jumpserver-installer-v2.13.1]# egrep -v "^#|^$" /etc/redis.conf                      
bind 0.0.0.0
protected-mode no
port 6379
tcp-backlog 511
timeout 0
tcp-keepalive 300
daemonize yes
pidfile "/var/run/redis.pid"
loglevel notice
logfile "/var/log/redis/redis.log"
databases 16
always-show-logo no
set-proc-title yes
proc-title-template "{title} {listen-addr} {server-mode}"
stop-writes-on-bgsave-error yes
rdbcompression yes
rdbchecksum yes
dbfilename "dump.rdb"
rdb-del-sync-files no
dir "/var/lib/redis"
replicaof 10.20.100.113 6379
masterauth "123456"
replica-serve-stale-data yes
replica-read-only yes
repl-diskless-sync no
repl-diskless-sync-delay 5
repl-diskless-load disabled
repl-ping-replica-period 10
repl-timeout 60
repl-disable-tcp-nodelay no
replica-priority 100
acllog-max-len 128
requirepass "123456"
maxmemory 4gb
maxmemory-policy allkeys-lru
lazyfree-lazy-eviction no
lazyfree-lazy-expire no
lazyfree-lazy-server-del no
replica-lazy-flush no
lazyfree-lazy-user-del no
lazyfree-lazy-user-flush no
oom-score-adj no
oom-score-adj-values 0 200 800
disable-thp yes
appendonly yes
appendfilename "appendonly.aof"
appendfsync everysec
no-appendfsync-on-rewrite no
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
aof-load-truncated yes
aof-use-rdb-preamble yes
lua-time-limit 5000
slowlog-log-slower-than 10000
slowlog-max-len 128
latency-monitor-threshold 0
notify-keyspace-events ""
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
list-max-ziplist-size -2
list-compress-depth 0
set-max-intset-entries 512
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
hll-sparse-max-bytes 3000
stream-node-max-bytes 4kb
stream-node-max-entries 100
activerehashing yes
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit replica 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
hz 10
dynamic-hz yes
aof-rewrite-incremental-fsync yes
rdb-save-incremental-fsync yes
jemalloc-bg-thread yes
save 3600 1
save 300 100
save 60 10000

100.200.100.112:

[root@JUMPSER-100-200-100-112 jumpserver-installer-v2.13.1]# egrep -v "^#|^$" /etc/redis.conf 
bind 0.0.0.0
protected-mode no
port 6379
tcp-backlog 511
timeout 0
tcp-keepalive 300
daemonize yes
pidfile "/var/run/redis.pid"
loglevel notice
logfile "/var/log/redis/redis.log"
databases 16
always-show-logo no
set-proc-title yes
proc-title-template "{title} {listen-addr} {server-mode}"
stop-writes-on-bgsave-error yes
rdbcompression yes
rdbchecksum yes
dbfilename "dump.rdb"
rdb-del-sync-files no
dir "/var/lib/redis"
masterauth "123456"
replica-serve-stale-data yes
replica-read-only yes
repl-diskless-sync no
repl-diskless-sync-delay 5
repl-diskless-load disabled
repl-ping-replica-period 10
repl-timeout 60
repl-disable-tcp-nodelay no
replica-priority 100
acllog-max-len 128
requirepass "123456"
maxmemory 4gb
maxmemory-policy allkeys-lru
lazyfree-lazy-eviction no
lazyfree-lazy-expire no
lazyfree-lazy-server-del no
replica-lazy-flush no
lazyfree-lazy-user-del no
lazyfree-lazy-user-flush no
oom-score-adj no
oom-score-adj-values 0 200 800
disable-thp yes
appendonly yes
appendfilename "appendonly.aof"
appendfsync everysec
no-appendfsync-on-rewrite no
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
aof-load-truncated yes
aof-use-rdb-preamble yes
lua-time-limit 5000
slowlog-log-slower-than 10000
slowlog-max-len 128
latency-monitor-threshold 0
notify-keyspace-events ""
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
list-max-ziplist-size -2
list-compress-depth 0
set-max-intset-entries 512
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
hll-sparse-max-bytes 3000
stream-node-max-bytes 4kb
stream-node-max-entries 100
activerehashing yes
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit replica 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
hz 10
dynamic-hz yes
aof-rewrite-incremental-fsync yes
rdb-save-incremental-fsync yes
jemalloc-bg-thread yes
save 3600 1
save 300 100
save 60 10000

100.200.100.113:

[root@JUMPSER-100-200-100-113 0]# egrep -v "^#|^$" /etc/redis.conf 
bind 0.0.0.0
protected-mode no
port 6379
tcp-backlog 511
timeout 0
tcp-keepalive 300
daemonize yes
pidfile "/var/run/redis.pid"
loglevel notice
logfile "/var/log/redis/redis.log"
databases 16
always-show-logo no
set-proc-title yes
proc-title-template "{title} {listen-addr} {server-mode}"
stop-writes-on-bgsave-error yes
rdbcompression yes
rdbchecksum yes
dbfilename "dump.rdb"
rdb-del-sync-files no
dir "/var/lib/redis"
masterauth "123456"
replica-serve-stale-data yes
replica-read-only yes
repl-diskless-sync no
repl-diskless-sync-delay 5
repl-diskless-load disabled
repl-ping-replica-period 10
repl-timeout 60
repl-disable-tcp-nodelay no
replica-priority 100
acllog-max-len 128
requirepass "123456"
maxmemory 4gb
maxmemory-policy allkeys-lru
lazyfree-lazy-eviction no
lazyfree-lazy-expire no
lazyfree-lazy-server-del no
replica-lazy-flush no
lazyfree-lazy-user-del no
lazyfree-lazy-user-flush no
oom-score-adj no
oom-score-adj-values 0 200 800
disable-thp yes
appendonly yes
appendfilename "appendonly.aof"
appendfsync everysec
no-appendfsync-on-rewrite no
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
aof-load-truncated yes
aof-use-rdb-preamble yes
lua-time-limit 5000
slowlog-log-slower-than 10000
slowlog-max-len 128
latency-monitor-threshold 0
notify-keyspace-events ""
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
list-max-ziplist-size -2
list-compress-depth 0
set-max-intset-entries 512
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
hll-sparse-max-bytes 3000
stream-node-max-bytes 4kb
stream-node-max-entries 100
activerehashing yes
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit replica 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
hz 10
dynamic-hz yes
aof-rewrite-incremental-fsync yes
rdb-save-incremental-fsync yes
jemalloc-bg-thread yes
save 3600 1
save 300 100
save 60 10000

部署redis-sentinel

100.200.100.111、112、113: 使用同一个配置

[root@JUMPSER-100-200-100-111 jumpserver-installer-v2.13.1]# egrep -v "^#|^$" /etc/redis-sentinel.conf
protected-mode no
port 26379
daemonize yes
pidfile "/var/run/redis-sentinel.pid"
logfile "/var/log/redis/sentinel.log"
dir "/tmp"
sentinel monitor mymaster 100.200.100.113 6379 2
sentinel down-after-milliseconds mymaster 5000
sentinel auth-pass mymaster 123456
acllog-max-len 128
sentinel deny-scripts-reconfig yes
sentinel resolve-hostnames no
sentinel announce-hostnames no

启动redis和redis-sentinel

配置自启动项

[root@JUMPSER-100-200-100-113 0]# cat /etc/systemd/system/redis.service 
[Unit]
Description=Redis persistent key-value database
After=network.target
After=network-online.target
Wants=network-online.target

[Service]
Type=forking
ExecStart=/usr/local/redis/bin/redis-server /etc/redis.conf
PIDFile=/var/run/redis.pid
ExecReload=/bin/kill -s HUP $MAINPID
ExecStop=/bin/kill -s QUIT $MAINPID

[Install]
WantedBy=multi-user.target

[root@JUMPSER-100-200-100-113 0]# cat /etc/systemd/system/redis-sentinel.service 
[Unit]
Description=Redis Sentinel
After=network.target
After=network-online.target
Wants=network-online.target

[Service]
Type=forking
ExecStart=/usr/local/redis/bin/redis-sentinel /etc/redis-sentinel.conf
PIDFile=/var/run/redis-sentinel.pid
ExecReload=/bin/kill -s HUP $MAINPID
ExecStop=/bin/kill -s QUIT $MAINPID

[Install]
WantedBy=multi-user.target

开机自启动

systemctl  enable  redis  redis-sentinel

启动redis

systemctl  start  redis  redis-sentinel

验证集群

redis-cli -h 127.0.0.1 -a 123456 info Replication
# Replication
role:master
connected_slaves:2
slave0:ip=100.200.100.111,port=6379,state=online,offset=244414,lag=1
slave1:ip=100.200.100.112,port=6379,state=online,offset=244414,lag=0
master_failover_state:no-failover
master_replid:b7f646c4f8e0d4f1d036115f24c903406cb3ca7e50
master_replid2:fef7c063c9500ec000709ab51dd03d6a8cc88fd1f9
master_repl_offset:244414
second_repl_offset:21938
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:17657
repl_backlog_histlen:226758

关闭master节点，看某个slave节点是否成为master，然后在启动刚才关闭的节点，看是否加入到集群。（步骤省略，各位看官自行测试吧 ～～）

安装keepalived

yum install -y keepalived

配置keepalived
100.200.100.111：

[root@JUMPSER-100-200-100-111 jumpserver-installer-v2.13.1]# cat  /etc/keepalived/keepalived.conf
! Configuration File for keepalived
global_defs {     
   router_id redis-111     
}

vrrp_script chk_redis {
  script "/usr/bin/redis-cli -h 127.0.0.1 -a 123456 info|grep role:master >/dev/null 2>&1" 
  interval 1
}

vrrp_instance redis {
  state BACKUP
  interface eth0
  virtual_router_id 79 #保持一致
  priority 98 #优先级
  nopreempt
  advert_int 1

  authentication {
    auth_type PASS
    auth_pass redis 
  }

  virtual_ipaddress {
    100.200.100.114
  }

  track_script {
    chk_redis
  }
}

100.200.100.112：

[root@JUMPSER-100-200-100-112 jumpserver-installer-v2.13.1]# cat  /etc/keepalived/keepalived.conf
! Configuration File for keepalived
global_defs {     
   router_id redis-112 
}

vrrp_script chk_redis {
  script "/usr/bin/redis-cli -h 127.0.0.1 -a 123456 info|grep role:master >/dev/null 2>&1" 
  interval 1
}

vrrp_instance redis {
  state BACKUP
  interface eth0
  virtual_router_id 79 #保持一致
  priority 99 #优先级
  nopreempt
  advert_int 1

  authentication {
    auth_type PASS
    auth_pass redis
  }

  virtual_ipaddress {
    100.200.100.114
  }

  track_script {
    chk_redis
  }
}

100.200.100.113：

[root@JUMPSER-100-200-100-113 ~]# cat  /etc/keepalived/keepalived.conf
! Configuration File for keepalived
global_defs {     
   router_id redis-113 
}

vrrp_script chk_redis {
  script "/usr/bin/redis-cli -h 127.0.0.1 -a 123456 info|grep role:master >/dev/null 2>&1"
  interval 1
}

vrrp_instance redis {
  state MASTER
  interface eth0
  virtual_router_id 79
  priority 100
  nopreempt
  advert_int 1

  authentication {
    auth_type PASS
    auth_pass redis
  }

  virtual_ipaddress {
    100.200.100.114
  }

  track_script {
    chk_redis
  }
}

启动keepalived

三台操作

systemctl  enable  keepalived
systemctl  start  keepalived

验证集群

[root@JUMPSER-100-200-100-111 jumpserver-installer-v2.13.1]#  ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:67:a0:b1 brd ff:ff:ff:ff:ff:ff
    inet 100.200.100.111/21 brd 100.200.103.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet 100.200.100.114/32 scope global eth0

首先关闭vip漂移到的节点，查看vip状态是否移除，使用以下命令
/usr/bin/redis-cli -h 127.0.0.1 -a 123456 info|grep role:master 查看master在那个节点上，同时查看vip是否存在这个节点上，有的话成功。 以上操作多刷几次！！

GeekXuShuo
关注
redis实现HA（High Available）的两种实现方式-Sentinel与Keepalived
路漫漫，水迢迢
05-03 4145
Sentinel先来说说Sentinel，Sentinel是redis自带的一种实现HA的方式，如果在实际应用中这种方式用的比较少，比较流行的还是KeepAlived。 Redis 的 Sentinel 系统用于管理多个 Redis 服务器（instance）， 该系统执行以下三个任务： ● 监控（Monitoring）： Sentinel 会不断地检查你的主服务器和从服务器是否运作正常。
redis高可用：keepalived+redis主从部署
热门推荐
隙光
08-11 1万+
Redis主从+Keepalived
Redis6.2.5 集群安装
qq_42409495的博客
10-15 242
1Redis简介 1.1 什么是redis Redis 是一种开源（BSD 许可）、内存中数据结构存储，用作数据库、缓存和消息代理。Redis 提供了诸如字符串、散列、列表、集合、带范围查询的排序集合、位图、超级日志、地理空间索引和流等数据结构。Redis 内置复制、Lua 脚本、LRU 驱逐、事务和不同级别的磁盘持久化，并通过 Redis Sentinel 和 Redis Cluster 自动分区提供高可用性。 1.2 Redis 集群数据分片 Redis 集群不使用一致散列，而是一种不同形式的分
Redis高可用方案：使用Keepalived实现主备双活
最新发布
xichji的专栏
08-30 726
在该目录下创建scripts_redis文件夹，目录 /etc/keepalived/scripts_redis，将 redis_stop.sh 、redis_master.sh、redis_fault.sh 、redis_check.sh 、redis_backup.sh 放入scripts_redis文件目录下。首先确保两台服务器都安装了Redis服务，Redis的端口号和密码两台服务器必须保持一致。首先需要修改备服务器redis配置文件，把备服务器redis挂载到主服务器redis下面实现主从配置。
redis+Sentinel+keepalived 实现集群高可用
weixin_34138056的博客
02-20 232
Redis 版本 Redis server v=3.2.12 sha=00000000:0 malloc=jemalloc-3.6.0 bits=64 build=7897e7d0e13773fKeepalived 版本 Keepalived v1.3.5 (03/19,2017), git commit v1.3.5-6-g6fa32f2原理：Keepalived 由...
Redis主从配置及使用KeepAlived实现Redis高可用
imxiangzi的专栏
09-01 1271
一：环境介绍 Master: 172.16.206.29 Slave: 172.16.206.28 Virtural IP Address (VIP): 172.16.206.250 二：设计思路： 当 Master 与 Slave 均运作正常时, Master负责服务，Slave负责Standby； 当 Master 挂掉，Slave 正常时, Slave接管服务，有写权限，同时
Redis解析之Keepalived
傲然君
08-04 485
1、VIP概念：VIP（虚拟IP），指不与特定计算机或计算机网卡相连的IP地址。 若配置了VIP，则主机同时拥有VIP和真实IP，并且使用任一IP都可与主机相连。目的：VIP一般用作实现HA(High Availability，高可靠性)，比如当集群主服务器发生故障无法对外提供服务时，可动态将VIP切换至备用机。2、Keepalived概念：Keepalived是一种实现IP漂移的方法，具体来讲它
Redis哨兵主从模式+keepalived.docx
12-12
Redis哨兵主从模式是指 Redis 的一种高可用性解决方案，通过哨兵模式实现自动故障切换和虚拟IP漂移，以提供高可用性的Redis服务。下面是相关知识点的详细解释： 一、Redis主从复制模式 Redis主从复制模式是一种...
Keepalived+redis高可用主从-Keepalived的配置
01-07
Keepalived+redis高可用主从，本技术文档主要是Keepalived的配置，redis主从配置可以看我的文章https://blog.csdn.net/qq_41709494/article/details/116382183
Redis + Keepalived主从集群的搭建及故障转移
ECHO_FOLLOW_HEART的专栏
06-06 4043
Redis + Keepalived主从集群的搭建及故障转移设计思路： 当 Master 与 Slave 均运作正常时, Master负责服务，Slave负责Standby； 当 Master 挂掉，Slave 正常时, Slave接管服务，同时关闭主从复制功能； 当 Master 恢复正常，则从Slave同步数据，同步数据之后关闭主从复制功能，恢复Master身份，于此同时Slave等待Maste
Redis哨兵主从模式+keepalived
12-12
在Java开发中，通过Jedis或Lettuce等Redis客户端库，可以方便地与Redis Sentinel+Keepalived集群进行交互，实现高可用的数据存储和读写操作。 总结，Redis哨兵主从模式与Keepalived的结合是企业级应用中保障数据...
redis主从配置及通过keepalived实现redis自动切换
10-03
redis主从配置及通过keepalived实现redis自动切换 常用命令及故障分析
redis+Keepalived实现Redis高可用性
10-26
redis+Keepalived实现Redis高可用性 主要包含两个文件： 1、安装文档 2、各种脚本文件
redis+keepalived 实现 HA
lester的专栏
10-19 1328
转载自：http://blog.sina.com.cn/s/blog_51cd5b6f01014r7p.html redis 安装配置到主从及ha的实现 sed -i '/^\$/ aexclude=*.i?86' /etc/yum.conf yum remove \*.i\?86 -y yum groupinstall "Development Libraries" "Developme
Redis 高可用方案Keepalived
任何技能都是从模仿开始，逐步升华。
04-09 2618
在redis3.0没有现世之前，为了提高redis的高可用性，通常的做法是采用HAProxy或Keepalived来实现故障自动转移，事实上如果是做Failover而非负载均衡的话，Keepalived的效率肯定是超过HAProxy的，所以下面我们采用Keepalived的方案。
Keepalived+Redis安装
weixin_34372728的博客
09-17 95
为什么80%的码农都做不了架构师？>>> ...
Redis + Keepalived 实现双机主从互备【互为主从、主从自动切换】
liuqw231的专栏
02-16 4192
实际生产中，系统压力不大且仅两台物理服务器；实际一个Redis服务完全够用，但为了高可用及容灾备份，又不够哨兵模式的三台，所以做此实现方案。
keepalived实现redis双主备份
weixin_34360651的博客
12-17 489
现在的生产环境基本上都采用主备方式，而如何实现redis的主备呢？一般情况下，redis实现主从复制比较简单，只需要在从服务器的配置文件里配置 "slaveof"即可。但这样存在一个问题：主服务器挂掉时，可临时将业务地址转移到从服务器，但从服务器无法进行写操作。为解决这个问题，在网上查找了一些资料。主要有以下几种方案使用keepalived+监控脚本实现主备切换使用redi...
keepalived 实现redis 高可用
小菜鸟的博客
09-09 627
1、安装keepalived yum -y install keepalived 配置keepalived, 主节点和从节点都是BACKUP vim /etc/keepalived/keepalived.conf ! Configuration File for keepalived global_defs { router_id redis } # keepalived监控脚本 vrrp_script chk_redis { #keepalived 健康检测执行脚本 s
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值