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

[经验分享] Redis+keepalived 主从搭建

[复制链接]

尚未签到

发表于 2018-11-6 12:50:24 | 显示全部楼层 |阅读模式
  设计思路:
  redis 主和 redis从  正常同步;
  redis主keepalived 启动,执行redis_master.sh脚本,vip在自己身上;
  redis 从keepalived 启动,执行redis_slave.sh脚本;
  redis主服务关闭,则redis主执行redis_fault.sh脚本, vip落在ipredis 从上,redis从执行redis_master.sh脚本,变成主;
  redis主服务开启,则redis主执行redis_slave.sh脚本变成从,vip还在redis 从上,还是主;
  redis从服务关闭,则redis从执行redis_fault.sh脚本, vip落在redis主上,redis主执行redis_master.sh脚本,变成主;
  redis从服务开启,则redis从执行redis_slave.sh脚本变成从, vip还在redis主上,redis主继续做主,此时为redis初试主从状态;
  环境:
  192.168.1.39 redis
  192.168.1.52 redis-slave
  192.168.1.75 vip
  一:安装keepalived
  (redis和redis-slave两台服务器都安装)
  yum -y install ipvsadm keepalived
  二:安装redis
  (redis和redis-slave两台服务器都安装)
  tar -zxvf redis-2.4.17.tar.gz
  cd redis-2.4.17
  ./configure
  make
  make install
  redis-slve只需注意一点
  [root@redis bin]# vim /etc/redis.conf
  slaveof 192.168.1.39 6379
  三:通过Keepalived实现Redis Failover自动故障切换
  修改Master和Slave的/etc/hosts文件
  [root@redis rc.d]# cat /etc/hosts
  192.168.1.39   redis
  192.168.1.52   redis-slave
  Master上是
  [root@redis rc.d]# cat /etc/sysconfig/network
  NETWORKING=yes
  HOSTNAME=redis
  Slave上是
  [root@redis-slave linux]# cat /etc/sysconfig/network
  NETWORKING=yes
  HOSTNAME=redis-slave
  修改完主机名重启机器生效
  默认安装完成keepalived之后是没有配置文件的,因此我们需要手动创建:
  首先,在Master上创建如下配置文件:
  [root@redis  linux]# vim /etc/keepalived/keepalived.conf
  global_defs {
  notification_email {
  liyongshan213@sina.com
  }
  notification_email_from keepalived@redis
  router_id redis
  }
  vrrp_script chk_redis {
  script "/etc/keepalived/scripts/redis_check.sh"
  interval 1
  }
  vrrp_instance mes_Redis {
  state MASTER
  interface eth0
  garp_master_delay 10
  smtp_alert
  virtual_router_id 3
  priority 100
  nopreempt
  advert_int 1
  authentication {
  auth_type PASS
  auth_pass 1111
  }
  virtual_ipaddress {
  192.168.1.75
  }
  track_script {
  chk_redis
  }
  notify_master /etc/keepalived/scripts/redis_master.sh
  notify_backup /etc/keepalived/scripts/redis_slave.sh
  notify_fault  /etc/keepalived/scripts/redis_fault.sh
  notify_stop   /etc/keepalived/scripts/redis_stop.sh
  }
  然后,在Slave上创建如下配置文件:
  [root@redis-slave linux]# vim /etc/keepalived/keepalived.conf
  global_defs {
  notification_email {
  liyongshan213@sina.com
  }
  notification_email_from keepalived@redis-slave
  router_id redis-salve
  }
  vrrp_script chk_redis {
  script "/etc/keepalived/scripts/redis_check.sh"
  interval 1
  }
  vrrp_instance mes_Redis {
  state BACKUP
  interface eth0
  garp_master_delay 10
  smtp_alert
  virtual_router_id 3
  priority 90
  nopreempt
  advert_int 1
  authentication {
  auth_type PASS
  auth_pass 1111
  }
  virtual_ipaddress {
  192.168.1.237
  }
  track_script {
  chk_redis
  }
  notify_master /etc/keepalived/scripts/redis_master.sh
  notify_backup /etc/keepalived/scripts/redis_slave.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
  ALIVE=`/usr/local/bin/redis-cli PING`
  if [ "$ALIVE" == "PONG" ]; then
  echo $ALIVE
  exit 0
  else
  echo $ALIVE
  exit 1
  fi
  编写以下负责运作的关键脚本:
  notify_master /etc/keepalived/scripts/redis_master.sh
  notify_backup /etc/keepalived/scripts/redis_slave.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="/usr/local/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.1.236 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_slave.sh
  #!/bin/bash
  REDISCLI="/usr/local/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.1.236 6379 >> $LOGFILE  2>&1
  接着,在Redis Slave上创建notity_master与notify_backup脚本:
  vim /etc/keepalived/scripts/redis_master.sh
  #!/bin/bash
  REDISCLI="/usr/local/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.1.235 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_slave.sh
  #!/bin/bash
  REDISCLI="/usr/local/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.1.235 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
  在Master与Slave给脚本都加上可执行权限:
  chmod +x /etc/keepalived/scripts/*.sh
  脚本创建完成以后,我们开始按照如下流程进行测试:
  1.启动Master上的Redis
  [root@redis ~]# /usr/local/bin/redis-server /etc/redis.conf
  2.启动Slave上的Redis
  [root@redis ~]# /usr/local/bin/redis-server /etc/redis.conf
  3.启动Master上的Keepalived
  /etc/init.d/keepalived start
  4.启动Slave上的Keepalived
  /etc/init.d/keepalived start
  5.尝试通过VIP连接Redis:
  [root@redis ~]# /usr/local/bin/redis-cli -h 192.168.1.75 info
  role:master
  slave0:192.168.1.52,6379,online
  连接成功,Slave也连接上来了
  6.尝试插入一些数据:
  [root@redis ~]# /usr/local/bin/redis-cli -h 192.168.1.75 SET Hello Redis
  从VIP读取数据
  [root@redis ~]# /usr/local/bin/redis-cli -h 192.168.1.75 GET Hello
  "Redis"
  从Master读取数据
  [root@redis ~]# /usr/local/bin/redis-cli -h 192.168.1.39 GET Hello
  "Redis"
  从Slave读取数据
  [root@redis ~]# /usr/local/bin/redis-cli -h 192.168.1.52 GET Hello
  "Redis"
  下面,模拟故障产生:
  将Master上的Redis进程杀死:
  [root@redis ~]# /usr/local/bin/redis-cli shutdown
  查看Master上的Keepalived日志
  [root@redis scripts]# tail /var/log/keepalived-redis-state.log
  [fault]
  Thu Sep 27 08:29:01 CST 2012
  同时Slave上的日志显示:
  [root@redis-slave scripts]# tail /var/log/keepalived-redis-state.log
  [master]
  Thu Nov 15 12:06:04 CST 2012
  Being master....
  Run SLAVEOF cmd ...
  OK
  Run SLAVEOF NO ONE cmd ...
  OK
  然后我们可以发现,Slave已经接管服务,并且担任Master的角色了。
  ./redis-cli -h 192.168.1.75 info
  ./redis-cli -h 192.168.1.52 info
  role:master
  然后我们恢复Master的Redis进程
  主变成slave
  然后把52redis停掉
  39恢复主的角色,在把52redis开启
  恢复39是主,52是备
  自动切换成功!


运维网声明 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-631569-1-1.html 上篇帖子: 四、Java内存数据库实践之深入浅出Redis - Java Client - Jedis的使用 下篇帖子: redis搭建及简单使用
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

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

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

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

扫描微信二维码查看详情

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


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


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


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



合作伙伴: 青云cloud

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