设为首页 收藏本站
查看: 1023|回复: 0

[经验分享] 实现Redis高可用

[复制链接]
发表于 2018-11-5 09:46:21 | 显示全部楼层 |阅读模式
  利用keepalived实现redis高可用
  环境介绍:
  master: 192.168.0.100
  slave: 192.168.0.101
  vip(keepvlied虚拟IP): 192.168.0.200
  注:这里有一个坑
  就是在同一网段之间的Keepalived的配置文件中需要把 virtual_router_id 后面的值设置不同(范围是0-255),否则,keepalived在主从切换的时间会有问题,而且在/var/log/messages日志中
  会不断的写入日志,会把服务器写爆。
virtual_router_id 每一套都需要设置不同(范围是0-255)  当 Master 与 Slave 均运作正常时, Master负责服务,Slave负责Standby;
  当 Master 挂掉,Slave 正常时, Slave接管服务,同时关闭主从复制功能;
  当 Master 恢复正常,则从Slave同步数据,同步数据之后关闭主从复制功能,恢复Master身份,于此同时Slave等待Master同步数据完成之后,恢复Slave身份。
  然后依次循环。
  需要注意的是,这样做需要在Master与Slave上都开启本地化策略,否则在互相自动切换的过程中,未开启本地化的一方会将另一方的数据清空,造成数据完全丢失
在Master和Slave上安装Keepalived
yum install -y keepalived  首先,在Master上创建如下配置文件
! Configuration File for keepalived  
global_defs {
  
   router_id redis100
  
}
  
vrrp_script chk_redis
  
{
  
     script "/etc/keepalived/scripts/redis_check.sh 127.0.0.1 6379"
  
     interval 2
  
     timeout 2
  
     fall 3
  
}
  
vrrp_instance redis {
  
     state MASTER # master set to SLAVE also
  
     interface eth0
  
     virtual_router_id 50
  
     priority  150
  
     nopreempt # 非抢占模式,注:主与从必须同时设置为BACKUP
  
     advert_int 1
  
authentication {   #all node must same
  
         auth_type PASS
  
         auth_pass 1111
  
    }
  
    virtual_ipaddress {
  
192.168.0.200/24
  
    }
  
    track_script {
  
         chk_redis
  
    }
  
     notify_master "/etc/keepalived/scripts/redis_master.sh 127.0.0.1 192.168.0.101 6379"
  
     notify_backup "/etc/keepalived/scripts/redis_backup.sh 127.0.0.1 192.168.0.101 6379"
  
     notify_fault /etc/keepalived/scripts/redis_fault.sh
  
     notify_stop /etc/keepalived/scripts/redis_stop.sh
  
}
  然后,在Slave上创建如下配置文件:
! Configuration File for keepalived  

  
global_defs {
  
   router_id redis101
  
}
  
vrrp_script chk_redis
  
{
  
     script "/etc/keepalived/scripts/redis_check.sh 127.0.0.1 6379"
  
     interval 2
  
     timeout 2
  
     fall 3
  
}
  
vrrp_instance redis {
  
    state BACKUP
  
    interface eth0
  
    virtual_router_id 50
  
    priority  100
  
    advert_int 1
  
authentication {   #all node must same
  
        auth_type PASS
  
        auth_pass 1111
  
    }
  
    virtual_ipaddress {
  
    192.168.0.200/24
  
    }
  
    track_script {
  
         chk_redis
  
    }
  
    notify_master "/etc/keepalived/scripts/redis_master.sh 127.0.0.1 192.168.0.100 6379"
  
    notify_backup "/etc/keepalived/scripts/redis_backup.sh 127.0.0.1 192.168.0.100 6379"
  
    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
  
ALIVE=`/usr/redis/redis-cli -h $1 -p $2 PING`
  
LOGFILE="/var/log/keepalived-redis-check.log"
  
echo "[CHECK]" >> $LOGFILE
  
date >> $LOGFILE
  
if [ $ALIVE == "PONG" ]; then :
  
   echo "Success: redis-cli -h $1 -p $2 PING $ALIVE" >> $LOGFILE 2>&1
  
    exit 0
  
else
  
    echo "Failed:redis-cli -h $1 -p $2 PING $ALIVE " >> $LOGFILE 2>&1
  
    exit 1
  
fi
  编写以下负责运作的关键脚本
  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脚本:
  cat /etc/keepalived/scripts/redis_master.sh
#!/bin/bash  
REDISCLI="/usr/redis/redis-cli -h $1 -p $3"
  
LOGFILE="/var/log/keepalived-redis-state.log"
  
echo "[master]" >> $LOGFILE
  
date >> $LOGFILE
  
echo "Being master...." >> $LOGFILE 2>&1
  
echo "Run MASTER cmd ..." >> $LOGFILE 2>&1
  
$REDISCLI SLAVEOF $2 $3 >> $LOGFILE
  
sleep 10 #delay 10 s wait data async cancel sync
  
echo "Run SLAVEOF NO ONE cmd ..." >> $LOGFILE
  
$REDISCLI SLAVEOF NO ONE >> $LOGFILE 2>&1
  cat /etc/keepalived/scripts/redis_backup.sh
#!/bin/bash  
REDISCLI="/usr/redis/redis-cli"
  
LOGFILE="/var/log/keepalived-redis-state.log"
  
echo "[backup]" >> $LOGFILE
  
date >> $LOGFILE
  
echo "Run SLAVEOF cmd ..." >> $LOGFILE
  
$REDISCLI SLAVEOF $2 $3 >> $LOGFILE 2>&1
  
# echo "Being slave...." >> $LOGFILE 2>&1
  
sleep 15 #delay 15 s wait data sync exchange role
  接着,在Redis Slave上创建notity_master与notify_backup脚本:
  cat /etc/keepalived/scripts/redis_master.sh
#!/bin/bash  
REDISCLI="/usr/redis/redis-cli -h $1 -p $3"
  
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 $2 $3 >> $LOGFILE  2>&1
  
#echo "SLAVEOF $2 cmd can't excute ... " >> $LOGFILE
  
sleep 10 ##delay 15 s wait data sync exchange role
  
echo "Run SLAVEOF NO ONE cmd ..." >> $LOGFILE
  
$REDISCLI SLAVEOF NO ONE >> $LOGFILE 2>&1
  cat /etc/keepalived/scripts/redis_backup.sh
#!/bin/bash  
REDISCLI="/usr/redis/redis-cli"
  
LOGFILE="/var/log/keepalived-redis-state.log"
  
echo "[BACKUP]" >> $LOGFILE
  
date >> $LOGFILE
  
echo "Being slave...." >> $LOGFILE 2>&1
  
echo "Run SLAVEOF cmd ..." >> $LOGFILE 2>&1
  
$REDISCLI SLAVEOF $2 $3 >> $LOGFILE
  
sleep 100 #delay 10 s wait data async cancel sync
  
exit(0)
  然后在Master与Slave创建如下相同的脚本:
  cat /etc/keepalived/scripts/redis_fault.sh
#!/bin/bash  
LOGFILE=/var/log/keepalived-redis-state.log
  
echo "[fault]" >> $LOGFILE
  
date >> $LOGFILE
  cat /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 10.6.1.200 INFO  连接成功,Slave也连接上来了。
role:master  
slave0:192.168.0.101,6379,online
  6.尝试插入一些数据:
$ redis-cli -h 10.6.1.200 SET Hello Redis  
OK
  从VIP读取数据
$ redis-cli -h 10.6.1.200 GET Hello  
"Redis"
  从Master读取数据
$ redis-cli -h 10.6.1.143 GET Hello  
"Redis"
  从Slave读取数据
$ redis-cli -h 10.6.1.144 GET Hello  
"Redis"
  下面,模拟故障产生:
  将Master上的Redis停了
  本方来自:http://blog.csdn.net/huwei2003/article/details/41894197



运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-630941-1-1.html 上篇帖子: 监控redis和zookpeer服务脚本 并且python发送邮件 下篇帖子: 自己汇总的redis使用详解
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表