keeplived高可用实践

最新推荐文章于 2022-10-27 21:50:41 发布
最新推荐文章于 2022-10-27 21:50:41 发布
阅读量456 收藏
点赞数
分类专栏： HA 文章标签： haproxy lvs nginx
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_42352759/article/details/104033885
版权

lvs-DR+keepalived高可用负载均衡

基于web轮询
设置后端vip和rs规则

cat vip.sh
#!/bin/bash
vip=192.168.146.233
mask='255.255.255.255'
dev=lo:1

case $1 in
start)
/usr/bin/echo 1 > /proc/sys/net/ipv4/conf/all/arp_ignore
/usr/bin/echo 1 > /proc/sys/net/ipv4/conf/lo/arp_ignore
/usr/bin/echo 2 >/proc/sys/net/ipv4/conf/all/arp_announce
/usr/bin/echo 2 > /proc/sys/net/ipv4/conf/lo/arp_announce
ifconfig $dev $vip netmask $mask
;;
stop)
ifconfig $dev down
echo 0 > /proc/sys/net/ipv4/conf/all/arp_ignore
echo 0 > /proc/sys/net/ipv4/conf/lo/arp_ignore
echo 0 > /proc/sys/net/ipv4/conf/all/arp_announce
echo 0 > /proc/sys/net/ipv4/conf/lo/arp_announce
;;
*)
echo "Usage: $(basename $0) start|stop"
exit 1
esac
echo $1

分别给后端主机安装好web服务器
检测意见启动的vip地址

LISTEN     0      128                               *:80  

[root@t2 ~]#ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.146.117  netmask 255.255.255.0  broadcast 192.168.146.255
        inet6 fe80::30bb:f79d:94ce:c295  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::6ad0:30dc:fdfe:acab  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::74ed:9546:e005:274c  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:49:e6:30  txqueuelen 1000  (Ethernet)
        RX packets 203771  bytes 20203621 (19.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 307945  bytes 27268747 (26.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo:1: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536   #vip地址
        inet 192.168.146.233  netmask 255.255.255.255
        loop  txqueuelen 1000  (Local Loopback)

keepalived主机配置

global_defs {
   notification_email {
     root@localhost
   }
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id LVS_DEVEL
   vrrp_skip_check_adv_addr
   #vrrp_strict
   vrrp_garp_interval 0
   vrrp_gna_interval 0
   vrrp_iptables  #关闭生成的iptalbes规则

}
vrrp_instance VI_1 {
    state MASTER
    interface eth0
    virtual_router_id 80
    priority 100
    advert_int 1
    unicast_src_ip 192.168.146.97 #设置单播访问
    unicast_peer {
    192.168.146.107
    }
    authentication {
        auth_type PASS
        auth_pass 1111qwer
    }

   virtual_ipaddress {   #vip keepalived浮动的ip地址
     192.168.146.233 dev eth0 label eth0:1
    }

}
    virtual_server 192.168.146.233 80 {  #后端vip和keepalived相同
      delay_loop 3
      lb_algo rr #调度算法 实现简单轮询
      lb_kind DR #lvs-DR模式
      protocol TCP
      #persistence_timeout

    sorry_server 192.168.146.107 80  #道歉服务器
    real_server 192.168.146.126 80 { #后端真是webIP主机
       weight 1
       TCP_CHECK {
       connect_timeout 5
       nb_get_retry 3
       delay_beefore_retry 3
       connect_port 80  #基于tcp端口检测
       }
     }
    real_server 192.168.146.117 80 {
       weight 1
       TCP_CHECK {
       connect_timeout 5
       nb_get_retry 3
       delay_beefore_retry 3
       connect_port 80
       }

     }
}

访问测试

ipvsadm -Ln 
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  192.168.146.233:80 rr
  -> 192.168.146.117:80           Route   1      0          0         
  -> 192.168.146.126:80           Route   1      0          0         
[root@t1 ~]#ipvsadm -Ln  --stats
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port               Conns   InPkts  OutPkts  InBytes OutBytes
  -> RemoteAddress:Port
TCP  192.168.146.233:80                  8       48        0     3192        0
  -> 192.168.146.117:80                  4       24        0     1596        0
  -> 192.168.146.126:80                  4       24        0     1596        0


[root@t1 ~]#while true;do curl http://192.168.146.233;sleep 0.5;done
77777777777777777777777777777
6666666666666666
77777777777777777777777777777
6666666666666666
77777777777777777777777777777
6666666666666666
77777777777777777777777777777
6666666666666666

基于http状态检测
keepalived代码

    virtual_server 192.168.146.233 80 {
      delay_loop 3
      lb_algo rr
      lb_kind DR
      protocol TCP
      #persistence_timeout

    sorry_server 192.168.146.107 80
    real_server 192.168.146.126 80 {
       weight 1
       HTTP_GET {
       url {
         path /index.html
         status_code 200
         }
       }
       connect_timeout 5
       nb_get_retry 3
       delay_beefore_retry 3
       }

    real_server 192.168.146.117 80 {
       weight 1
       HTTP_GET {
       url {
         path /index.html  #检测后端web服务器/index.html是否访问正常为200,否则不予调度
         status_code 200
         }
       }
       connect_timeout 5
       nb_get_retry 3
       delay_beefore_retry 3
       }
}

实例测试

#while true;do curl   http://192.168.146.233/index.html;sleep 0.5;done 
77777777777777777777777777777
6666666666666666
77777777777777777777777777777
6666666666666666
77777777777777777 #此时访问正常
6666666666666666
            <div class="logos">
                <a href="http://nginx.net/"><img
                    src="/nginx-logo.png"
                    alt="[ Powered by nginx ]"
                    width="121" height="32" /></a>

                <a href="http://fedoraproject.org/"><img 
                    src="/poweredby.png"
                    alt="[ Powered by Fedora ]" 
                    width="88" height="31" /></a>
            </div>
        </div>
    </body>
</html>  #异常

6666666666666666
6666666666666666
6666666666666666 #异常后直接不再调度到该7777地址
6666666666666666
6666666666666666
6666666666666666
6666666666666666
6666666666666666
6666666666666666
6666666666666666
77777777777777777777777777777  #恢复后
6666666666666666
77777777777777777777777777777
6666666666666666

[root@t2 /usr/share/nginx/html]#ss -tnl
State      Recv-Q Send-Q                Local Address:Port                               Peer Address:Port              
LISTEN     0      128                               *:80   #80端口一直是开启的表示服务没有宕机                                         *:*                  
LISTEN     0      128                               *:22                                            *:*                  
LISTEN     0      100                       127.0.0.1:25                                            *:*                  
LISTEN     0      128                              :::80                                           :::*                  
LISTEN     0      128                              :::22                                           :::*                  
LISTEN     0      100                             ::1:25                                           :::*                  
[root@t2 /usr/share/nginx/html]#ls
404.html  50x.html  en-US  error  icons  img  index.html1  nginx-logo.png  poweredby.png
[root@t2 /usr/share/nginx/html]#mv index.html{,1}  #错误原因，我们更改了检测的uri地址
[root@t2 /usr/share/nginx/html]#mv index.html1 index.html #恢复后访问正常

基于第三方仲裁判断检测master或slave上的文件或文件夹是否存在完成vip自动切换

   vrrp_script chk_file {  #在global_dafs之外设置
   script "/bin/bash -c '[[ -f /etc/keepalived/file.txt ]]' && exit 7 || exit 0"  #脚本路径或shell命令
     interval 1 #间隔时间默认1s
     weight -80 #权重，检测失败后会权重相加，权重可以为负数即相加后降低本机权重
     fall 3 #脚本几次失败后转换为失败
     rise 5 #检测成功后，几次标记为成功
     timeout 2
   }

vrrp_instance VI_1 {  
    state MASTER
    interface eth0
    virtual_router_id 80
    priority 100
    advert_int 1
    unicast_src_ip 192.168.146.97
    unicast_peer {
    192.168.146.107
    }
    authentication {
        auth_type PASS
        auth_pass 1111qwer
    }

   virtual_ipaddress {  
     192.168.146.233 dev eth0 label eth0:1
    }



   track_script {  #引用定义好的脚本
     chk_file
   }

日志检测

Jan 19 22:09:42 t0 Keepalived_vrrp[10413]: Script `chk_file` now returning 1  #文件不存在
Jan 19 22:09:44 t0 Keepalived_vrrp[10413]: VRRP_Script(chk_file) failed (exited with status 1)
Jan 19 22:09:44 t0 Keepalived_vrrp[10413]: (VI_1) Changing effective priority from 100 to 20
Jan 19 22:09:47 t0 Keepalived_vrrp[10413]: (VI_1) Master received advert from 192.168.146.107 with higher priority 80, ours 20
Jan 19 22:09:47 t0 Keepalived_vrrp[10413]: (VI_1) Entering BACKUP STATE
Jan 19 22:09:47 t0 Keepalived_vrrp[10413]: (VI_1) removing VIPs.



Jan 19 22:10:06 t0 Keepalived_vrrp[10413]: Script `chk_file` now returning 0  #文件存在
Jan 19 22:10:10 t0 Keepalived_vrrp[10413]: VRRP_Script(chk_file) succeeded
Jan 19 22:10:10 t0 Keepalived_vrrp[10413]: (VI_1) Changing effective priority from 20 to 100
Jan 19 22:10:10 t0 Keepalived_vrrp[10413]: (VI_1) received lower priority (80) advert from 192.168.146.107 - discarding
Jan 19 22:10:11 t0 Keepalived_vrrp[10413]: (VI_1) received lower priority (80) advert from 192.168.146.107 - discarding
Jan 19 22:10:12 t0 Keepalived_vrrp[10413]: (VI_1) received lower priority (80) advert from 192.168.146.107 - discarding
Jan 19 22:10:13 t0 Keepalived_vrrp[10413]: (VI_1) Receive advertisement timeout
Jan 19 22:10:13 t0 Keepalived_vrrp[10413]: (VI_1) Entering MASTER STATE
Jan 19 22:10:13 t0 Keepalived_vrrp[10413]: (VI_1) setting VIPs.

基于脚本检测haproxy是否存活

vrrp_script chk_haproxy {
   script "/etc/keepalived/chk_haproxy.sh"
     interval 1
     weight -80
     fall 3
     rise 5
     timeout 2
   }

vrrp_instance VI_1 {
    state MASTER
    interface eth0
    virtual_router_id 80
    priority 100
    advert_int 1
    unicast_src_ip 192.168.146.97
    unicast_peer {
    192.168.146.107
    }
    authentication {
        auth_type PASS
        auth_pass 1111qwer
    }

   virtual_ipaddress {
     192.168.146.233 dev eth0 label eth0:1
    }



track_script {
     chk_haproxy
   }


}

chmod a+x /etc/keepalived/chk_haproxy.sh

[root@t0 /etc/keepalived]#cat /etc/keepalived/chk_haproxy.sh 
#!/bin/bash
/usr/bin/killall -0 haproxy

keepalived故障自动脚本实例

[root@t0 /etc/keepalived]#cat chk_keepalived.sh 
#!/bin/bash
ps aux |grep -v grep  | grep -v chk_keepalived.sh  |grep keepalived
if [  $? -eq 0 ];then
   echo keepalived is running
else
   systemctl restart keepalived
fi

* * * * * /usr/bin/bash /etc/keepalived/chk_keepalived.sh
goo flush. org
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
七章——Keepalived双机热备（应用——linux防护与群集）
MKC__jiaoq的博客
09-04 1717
三期总目录链接
KeepAlive + nginx的配置记录
weixin_43620243的博客
12-19 552
安装过程： yum install libnl libnl-devel openssl-devel -y wget http://www.keepalived.org/software/keepalived-2.0.10.tar.gz tar zxf keepalived-2.0.10.tar.gz cd keepalived-2.0.10 ./configure --prefix=/usr/lo...
linux配置虚拟IP--VIP
热门推荐
chengxuyuanyonghu的专栏
10-30 4万+
1，手动添加vip1,ifconfig查看当前活动网卡。如：eth02,执行ifconfig eth0:0 166.111.69.100 netmask 255.255.255.0 up进行vip添加3，执行ifconfig查看是否生效4，测试 ping 166.111.69.1005,写在/etc/rc.local里进行开机自动设置2，第三方工具keepalived增加vip1，下载与安装安装：...
docker部署minio对象存储集群
IT
12-22 8026
docker部署minio集群 准备4个节点，配置时间同步，关闭防火墙和selinux。 node1 192.168.92.10 node2 192.168.92.11 node3 192.168.92.12 node4 192.168.92.13 安装docke yum install -y yum-utils device-mapper-persistent-data lvm2 yum-config-manager --add-repo https://mirrors.aliyun.com/docke
keepalived问题汇总及解决方法
guiripei的专栏
12-16 5800
系统追求高可用，采用 keepalived + nginx 实现前置代理主机互备，部署过程中踩了几个坑，折腾了两天才搞定。现将问题及解决方法整理如下，供老铁们参考。 主机环境是CentOS Linux release 7.9.2009 (Core)，以root用户全程操作，采用yum -y install keepalived 命令安装keepalived。 keepalived运行状态查看及启停命令为： systemctl status keepalived systemctl stop keepa.
mysql+keeplived高可用
09-23
这个文档是工作实践中，整理的手册，部署和问题的解决都很详细，仅供参考
Windows server通过自身故障转移群集技术实现高可用详细步骤（mysql举例）
08-15
通过Windows故障转移群集技术实现mysql双机热备高可用功能，步骤详细
生产环境-Mysql高可用配置（dble+mysql+keeplived）.pdf
04-29
1.体系 dble+mysql+keeplived 2.机器与软件描述 mysql01(172.28.8.65) mysql02(172.28.8.61) dble01(172.28.8.62) ...keeplived01(172.28.8.62) ...keeplived02(172.28.8.63) ...3.keeplived保证高可用容灾
keepalived+nginx高可用实现方法示例
09-29
【keepalived+nginx高可用实现方法示例】 在构建高可用性Web服务时，`keepalived`和`nginx`的结合使用是常见的解决方案。本文将深入探讨这两种技术如何协同工作，确保服务的连续性和稳定性。 1. **keepalived介绍*...
Haproxy+Keeplived做Mysql和web负载高可用
02-19
在构建高可用性系统时，Haproxy和Keepalived是两种常见的工具，它们常被用来确保MySQL数据库和Web服务的稳定性和可靠性。Haproxy是一款高性能的负载均衡器，而Keepalived则是一个用于网络服务高可用性的系统，它可以...
Keepalived_vrrp[15699]: (VI_1): ip address associated with VRID 51 not present in MASTER advert : ..
Do
05-14 1391
描述： 配置完成启动后，无法ping同Vip， 打开日志显示如下： 166774 May 14 20:01:01 node32 Keepalived_vrrp[15699]: (VI_1): ip address associated with VRID 51 not present in MASTER advert : 172.16.18.253 166775 May 14 20:01:01 node32 Keepalived_vrrp[15699]: bogus VRRP packet rece
高可用集群 Keepalived 所有内容讲解
cp_dvd的博客
10-27 3739
vrrp 协议的软件实现，原生设计目的为了高可用 ipvs服务官网：http://keepalived.org/基于vrrp协议完成地址流动为vip地址所在的节点生成ipvs规则(在配置文件中预先定义)为ipvs集群的各RS做健康状态检测基于脚本调用接口完成脚本中定义的功能，进而影响集群事务，以此支持nginx、haproxy 等vrrp_script { #定义一个检测脚本，在global_defs 之外配置。
如何识别哪台keepalived机器上的priority优先级？
昊鼎王五的博客
07-29 3380
如何识别哪台keepavlied机器在漂移时的优先级顺序？ 是根据/etc/keepalived/keepalived.conf配置文件中的“priority”参数来决定的，数值越大的优先级越高,如下图 OK，解答完毕。...
keepalived 中关于 weight 和 preempt_delay 的实验
panbuhei
05-07 2077
keepalived中如果配置了权重(weight)的话，一定要注意权重(weight)和优先级(priority)的大小；即一个节点的 priority 减去 weight 必须小于另外一个节点的 priority。
VRRP出错原因
qq_48359654的博客
09-26 1632
【init状态表示为不可用状态】 1、两台交换机之间是否互连 2、互连链路的模式是否配置为trunk模式 3、检查VRRP的配置信息
keepalived配置抢占模式
MssGuo的博客
10-15 2228
keepalived的抢占模式
keeplived高可用web
最新发布
09-08
keepalived是一种用于实现高可用性的软件，主要用于在集群中检测服务的状态，并根据检测结果进行VIP（虚拟IP）的漂移。当keepalived进程异常时，会触发VIP漂移，将VIP转移到备用节点上，以确保网站的可用性。然而，...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值