通过Keepalived实现Redis Failover自动故障切换

环境介绍：

Master: 192.168.0.1

Slave: 192.168.0.2

Virtural IP Address (VIP): 192.168.0.253

设计思路：

当 Master 与 Slave 均运作正常时, Master负责服务，Slave负责Standby；

当 Master 挂掉，Slave 正时, Slave接管服务，同时关闭主从复制功能；

当 Master 恢复正常，则从Slave同步数据，同步数据之后关闭主从复制功能，恢复Master身份，于此同时Slave等待Master同步数据完成之后，恢复Slave身份。

然后依次循环。

需要注意的是，这样做需要在Master与Slave上都开启本地化策略，否则在互相自动切换的过程中，未开启本地化的一方会将另一方的数据清空，造成数据完全丢失。

下面，是具体的实施步骤：

在Master和Slave上安装Keepalived

$ yum install keepalived

修改Master和Slave的/etc/hosts文件

$ vim /etc/hosts

127.0.0.1 localhost

192.168.0.1 redis

192.168.0.2 redis-slave

默认安装完成keepalived之后是没有配置文件的，因此我们需要手动创建：

首先，在Master上创建如下配置文件：

$ vim /etc/keepalived/keepalived.conf

vrrp_script chk_redis {

script "/etc/keepalived/scripts/redis_check.sh" ###监控脚本

interval 2 ###监控时间

}

vrrp_instance VI_1 {

state MASTER ###设置为MASTER

interface eth0 ###监控网卡

virtual_router_id 51

priority 101 ###权重值

authentication {

auth_type PASS ###加密

auth_pass redis ###密码

}

track_script {

chk_redis ###执行上面定义的chk_redis

}

virtual_ipaddress {

192.168.0.253 ###VIP

}

notify_master /etc/keepalived/scripts/redis_master.sh

notify_backup /etc/keepalived/scripts/redis_backup.sh

notify_fault /etc/keepalived/scripts/redis_fault.sh

notify_stop /etc/keepalived/scripts/redis_stop.sh

}

然后，在Slave上创建如下配置文件：

$ vim /etc/keepalived/keepalived.conf

vrrp_script chk_redis {

script "/etc/keepalived/scripts/redis_check.sh" ###监控脚本

interval 2 ###监控时间

}

vrrp_instance VI_1 {

state BACKUP ###设置为BACKUP

interface eth0 ###监控网卡

virtual_router_id 51

priority 100 ###比MASTRE权重值低

authentication {

auth_type PASS

auth_pass redis ###密码与MASTRE相同

}

track_script {

chk_redis ###执行上面定义的chk_redis

}

virtual_ipaddress {

192.168.0.253 ###VIP

}

notify_master /etc/keepalived/scripts/redis_master.sh

notify_backup /etc/keepalived/scripts/redis_backup.sh

notify_fault /etc/keepalived/scripts/redis_fault.sh

notify_stop /etc/keepalived/scripts/redis_stop.sh

}

在Master和Slave上创建监控Redis的脚本

$ mkdir /etc/keepalived/scripts

$ vim /etc/keepalived/scripts/redis_check.sh

#!/bin/bash

0ALIVE=`/opt/redis/bin/redis-cli PING`

if [ "$ALIVE" == "PONG" ]; then

echo $ALIVE

exit 0

else

echo $ALIVE

exit 1

编写以下负责运作的关键脚本：

notify_master /etc/keepalived/scripts/redis_master.sh

notify_backup /etc/keepalived/scripts/redis_backup.sh

notify_fault /etc/keepalived/scripts/redis_fault.sh

notify_stop /etc/keepalived/scripts/redis_stop.sh

因为Keepalived在转换状态时会依照状态来呼叫：

当进入Master状态时会呼叫notify_master

当进入Backup状态时会呼叫notify_backup

当发现异常情况时进入Fault状态呼叫notify_fault

当Keepalived程序终止时则呼叫notify_stop

首先，在Redis Master上创建notity_master与notify_backup脚本：

$ vim /etc/keepalived/scripts/redis_master.sh

#!/bin/bash

REDISCLI="/opt/redis/bin/redis-cli"

LOGFILE="/var/log/keepalived-redis-state.log"

echo "[master]" >> $LOGFILE

date >> $LOGFILE

echo "Being master...." >> $LOGFILE 2>&1

echo "Run SLAVEOF cmd ..." >> $LOGFILE

$REDISCLI SLAVEOF 192.168.0.2 6379 >> $LOGFILE 2>&1

sleep 10 #延迟10秒以后待数据同步完成后再取消同步状态

echo "Run SLAVEOF NO ONE cmd ..." >> $LOGFILE

$REDISCLI SLAVEOF NO ONE >> $LOGFILE 2>&1

$ vim /etc/keepalived/scripts/redis_backup.sh

#!/bin/bash

REDISCLI="/opt/redis/bin/redis-cli"

LOGFILE="/var/log/keepalived-redis-state.log"

echo "[backup]" >> $LOGFILE

date >> $LOGFILE

echo "Being slave...." >> $LOGFILE 2>&1

sleep 15 #延迟15秒待数据被对方同步完成之后再切换主从角色

echo "Run SLAVEOF cmd ..." >> $LOGFILE

$REDISCLI SLAVEOF 192.168.0.2 6379 >> $LOGFILE 2>&1

接着，在Redis Slave上创建notity_master与notify_backup脚本：

$ vim /etc/keepalived/scripts/redis_master.sh

#!/bin/bash

REDISCLI="/opt/redis/bin/redis-cli"

LOGFILE="/var/log/keepalived-redis-state.log"

echo "[master]" >> $LOGFILE

date >> $LOGFILE

echo "Being master...." >> $LOGFILE 2>&1

echo "Run SLAVEOF cmd ..." >> $LOGFILE

$REDISCLI SLAVEOF 192.168.0.1 6379 >> $LOGFILE 2>&1

sleep 10 #延迟10秒以后待数据同步完成后再取消同步状态

echo "Run SLAVEOF NO ONE cmd ..." >> $LOGFILE

$REDISCLI SLAVEOF NO ONE >> $LOGFILE 2>&1

$ vim /etc/keepalived/scripts/redis_backup.sh

#!/bin/bash

REDISCLI="/opt/redis/bin/redis-cli"

LOGFILE="/var/log/keepalived-redis-state.log"

echo "[backup]" >> $LOGFILE

date >> $LOGFILE

echo "Being slave...." >> $LOGFILE 2>&1

sleep 15 #延迟15秒待数据被对方同步完成之后再切换主从角色

echo "Run SLAVEOF cmd ..." >> $LOGFILE

$REDISCLI SLAVEOF 192.168.0.1 6379 >> $LOGFILE 2>&1

然后在Master与Slave创建如下相同的脚本：

$ vim /etc/keepalived/scripts/redis_fault.sh

#!/bin/bash

LOGFILE=/var/log/keepalived-redis-state.log

echo "[fault]" >> $LOGFILE

date >> $LOGFILE

$ vim /etc/keepalived/scripts/redis_stop.sh

#!/bin/bash

LOGFILE=/var/log/keepalived-redis-state.log

echo "[stop]" >> $LOGFILE

date >> $LOGFILE

给脚本都加上可执行权限：

$ chmod +x /etc/keepalived/scripts/*.sh

脚本创建完成以后，我们开始按照如下流程进行测试：

1.启动Master上的Redis

$ /etc/init.d/redis start

2.启动Slave上的Redis

$ /etc/init.d/redis start

3.启动Master上的Keepalived

$ /etc/init.d/keepalived start

4.启动Slave上的Keepalived

$ /etc/init.d/keepalived start

5.尝试通过VIP连接Redis:

$ redis-cli -h 192.168.0.253 INFO

连接成功，Slave也连接上来了。

role:master

slave0:192.168.0.2,6379,online

6.尝试插入一些数据：

$ redis-cli -h 192.168.0.253 SET Hello Redis

从VIP读取数据

$ redis-cli -h 192.168.0.253 GET Hello

"Redis"

从Master读取数据

$ redis-cli -h 192.168.0.1 GET Hello

"Redis"

从Slave读取数据

$ redis-cli -h 192.168.0.2 GET Hello

"Redis"

下面，模拟故障产生：

将Master上的Redis进程杀死：

$ killall -9 redis-server

查看Master上的Keepalived日志

$ tail -f /var/log/keepalived-redis-state.log

[fault]

Thu Sep 27 08:29:01 CST 2012

同时Slave上的日志显示：

$ tail -f /var/log/keepalived-redis-state.log

[master]

Fri Sep 28 14:14:09 CST 2012

Being master....

Run SLAVEOF cmd ...

Run SLAVEOF NO ONE cmd ...

然后我们可以发现，Slave已经接管服务，并且担任Master的角色了。

$ redis-cli -h 192.168.0.253 INFO

$ redis-cli -h 192.168.0.2 INFO

role:master

然后我们恢复Master的Redis进程

$ /etc/init.d/redis start

查看Master上的Keepalived日志

$ tail -f /var/log/keepalived-redis-state.log

[master]

Thu Sep 27 08:31:33 CST 2012

Being master....

Run SLAVEOF cmd ...

Run SLAVEOF NO ONE cmd ...

同时Slave上的日志显示：

$ tail -f /var/log/keepalived-redis-state.log

[backup]

Fri Sep 28 14:16:37 CST 2012

Being slave....

Run SLAVEOF cmd ...

可以发现目前的Master已经再次恢复了Master的角色，故障切换以及自动恢复都成功了。

转载于:https://blog.51cto.com/304076020/1428280

通过Keepalived实现Redis Failover自动故障切换相关推荐

通过Keepalived实现Redis Failover自动故障切换功能(整理中) .
通过Keepalived实现Redis Failover自动故障切换功能分类: Linux 2013-06-21 16:44 1049人阅读评论(1) 收藏举报详细可参考http://heyl ...
通过Keepalived实现Redis Failover自动故障切换功能
参考资料: http://patrick-tang.blogspot.com/2012/06/redis-keepalived-failover-system.html http://deidara. ...
通过Keepalived实现Redis Failover自动故障切换功能[实践分享] =转载
http://heylinux.com/archives/1942.html
结合keepalived实现redis群集高可用故障自动切换
系统架构图: 我们所要实现的目的很简单, 104,107 为keepalive和redis主从架构,其余服务器比如105.106均为redis从库并且挂在vip 192.168.56.180下面. 主 ...
Redis主从自动failover
Redis主从架构持久化存在一个问题,即前次测试的结论,持久化需要配置在主实例上才能跨越实例保证数据不丢失,这样以来主实例在持久化数据到硬盘的过程中,势必会造成磁盘的I/O等待,经过实际测试,这个持久 ...
Redis主从配置及通过Keepalived实现Redis自动切换高可用
Redis主从配置及通过Keepalived实现Redis自动切换高可用 [日期:2014-07-23] 来源:Linux社区作者:fuquanjun [字体:大中小] 一:环境介绍: Mas ...
利用redis-sentinel+keepalived实现redis高可用
目标.需求: 为上层应用提供高可靠.低延迟.低(无限接近0)数据损失的Redis缓存服务方案概述: 采用同一网络内的三台主机(可以是物理主机.虚拟机或docker容器),要求三台主机之间都能相互访问 ...
基于keepalived对redis做高可用配置---转载
关于keepalived的详细介绍,请移步本人相关博客:http://wangfeng7399.blog.51cto.com/3518031/1405785 功能 ip地址安装软件主redis 1 ...
【Mongodb】 Replica set的自动故障切换
Replica set 为我们提供了自动故障切换功能,这个机制是由mongodb自己来操作的,它根据从库的优先级或者数据新鲜度(也就是最新的从主库同步数据的那个节点)来选择primary,而当以前的p ...
mysql replication 监控_MySQL之-Replication监控及自动故障切换的详细分析
1.服务器规划 Master:192.168.0.152 Slave: 192.168.0.153 192.168.0.154 监控服务器: 192.168.0.154 注意:真实生产环境最好有一台单 ...

通过Keepalived实现Redis Failover自动故障切换

通过Keepalived实现Redis Failover自动故障切换相关推荐

最新文章

热门文章