首页 / 负载均衡 / keepalived+nginx双机热备+负载均衡

keepalived+nginx双机热备+负载均衡

内容导读

互联网集市收集整理的这篇技术教程文章主要介绍了keepalived+nginx双机热备+负载均衡，小编现在分享给大家，供广大互联网技能从业者学习和参考。文章包含13877字，纯文字阅读大概需要20分钟。

内容图文

keepalived+nginx双机热备+负载均衡
最近因业务扩展，需要将当前的apache 转为nginx(web), 再在web前端放置nginx(负载均衡)。同时结合keepalived 对前端nginx实现HA。 nginx进程基于于Master+Slave(worker)多进程模型，自身具有非常稳定的子进程管理功能。在Master进程分配模式下，Master进程永远不进行业务处理，只是进行任务分发，从而达到Master进程的存活高可靠性，Slave(worker)进程所有的业务信号都由主进程发出，Slave(worker)进程所有的超时任务都会被Master中止，属于非阻塞式任务模型。 Keepalived是Linux下面实现VRRP 备份路由的高可靠性运行件。基于Keepalived设计的服务模式能够真正做到主服务器和备份服务器故障时IP瞬间无缝交接。二者结合，可以构架出比较稳定的软件lb方案。
技术分享
准备4台电脑来做这个实验:
192.168.232.132 web服务器 192.168.232.133 web服务器 192.168.232.134 keepalived nginx 192.168.232.135 keepalived nginx
虚拟IP (VIP)：192.168.232.16

134\135两个主机配置虚拟IP

下面以135为例：
vi /etc/sysconfig/network-scripts/ifcfg-eth2:0

[plain] view plaincopyprint ?

DEVICE=eth2:0
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=static
DNS1=192.168.232.2
IPADDR=192.168.232.16
NETMASK=255.255.255.0
GETWAY=192.168.232.2

DEVICE=eth2:0
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=static
DNS1=192.168.232.2
IPADDR=192.168.232.16
NETMASK=255.255.255.0
GETWAY=192.168.232.2

service network restart
使用ifconfig查看效果：

[plain] view plaincopyprint ?

eth2 Link encap:Ethernet HWaddr 00:0C:29:49:90:5B
inet addr:192.168.232.135 Bcast:192.168.232.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe49:905b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:66322 errors:0 dropped:0 overruns:0 frame:0
TX packets:31860 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:67624991 (64.4 MiB) TX bytes:2723877 (2.5 MiB)
Interrupt:19 Base address:0x2000
eth2:0 Link encap:Ethernet HWaddr 00:0C:29:49:90:5B
inet addr:192.168.232.16 Bcast:192.168.232.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:19 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:22622 errors:0 dropped:0 overruns:0 frame:0
TX packets:22622 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1236328 (1.1 MiB) TX bytes:1236328 (1.1 MiB)

eth2      Link encap:Ethernet  HWaddr 00:0C:29:49:90:5B  
          inet addr:192.168.232.135  Bcast:192.168.232.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fe49:905b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:66322 errors:0 dropped:0 overruns:0 frame:0
          TX packets:31860 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:67624991 (64.4 MiB)  TX bytes:2723877 (2.5 MiB)
          Interrupt:19 Base address:0x2000

eth2:0    Link encap:Ethernet  HWaddr 00:0C:29:49:90:5B  
          inet addr:192.168.232.16  Bcast:192.168.232.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:19 Base address:0x2000

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:22622 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22622 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1236328 (1.1 MiB)  TX bytes:1236328 (1.1 MiB)

说明生效了。

134\135两个主机安装keepalived和nginx

nginx安装：
1、导入外部软件库 rpm -Uvh http://dl.iuscommunity.org/pub/ius/stable/Redhat/6/i386/epel-release-6-5.noarch.rpm rpm -Uvh http://dl.iuscommunity.org/pub/ius/stable/Redhat/6/i386/ius-release-1.0-10.ius.el6.noarch.rpm rpm -Uvh http://nginx.org/packages/centos/6/noarch/RPMS/nginx-release-centos-6-0.el6.ngx.noarch.rpm 以下添加注释 mirrorlist=http://dmirr.iuscommunity.org/mirrorlist?repo=ius-el6&arch=$basearch 以下删除注释 #baseurl=http://dl.iuscommunity.org/pub/ius/stable/Redhat/5/$basearch 2、yum安装nginx yum install nginx
keepalived安装：
安装依赖 yum -y install gcc gcc+ gcc-c++ yum install popt-devel openssl openssl-devel libssl-dev libnl-devel popt-devel
安装内核 yum -y install kernel kernel-devel 当前kernel代码建立连接 ln -s /usr/src/kerners/2.6....../ /usr/src/linux
安装keepalived wget http://www.keepalived.org/software/keepalived-1.2.2.tar.gz tar -zxvf keepalived-1.2.2.tar.gz cd keepalived-1.2.2 ./configure make make install
拷贝相应的文件
cp /usr/local/sbin/keepalived /usr/sbin/ cp /usr/local/etc/rc.d/init.d/keepalived /etc/init.d/ cp /usr/local/etc/sysconfig/keepalived /etc/sysconfig/ cp -r /usr/local/etc/keepalived/ /etc/

配置keeplived和nginx主机

134/135执行都执行以下操作： vi /etc/nginx/conf.d/default.conf

[plain] view plaincopyprint ?

server {
listen 8088;
server_name localhost;
location / {
root /var/www/html;
index index.html index.htm;
}
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /usr/share/nginx/html;
}
}

server {
    listen       8088;
    server_name  localhost;

    location / {
        root   /var/www/html;
        index  index.html index.htm;
    }

    error_page   500 502 503 504  /50x.html;
    location = /50x.html {
        root   /usr/share/nginx/html;
    }
}

135执行以下操作： vi /var/www/html/index.html

[plain] view plaincopyprint ?

<html>
<head>
<title>Welcome to nginx!</title>
</head>
<body bgcolor="white" text="black">
<center><h1>Welcome to nginx! 192.168.232.135</h1></center>
</body>
</html>

<html>  
<head>  
<title>Welcome to nginx!</title>  
</head>  
<body bgcolor="white" text="black">  
<center><h1>Welcome to nginx! 192.168.232.135</h1></center>  
</body>  
</html>

134执行以下操作： vi /var/www/html/index.html

[plain] view plaincopyprint ?

<html>
<head>
<title>Welcome to nginx!</title>
</head>
<body bgcolor="white" text="black">
<center><h1>Welcome to nginx! 192.168.232.134</h1></center>
</body>
</html>

<html>  
<head>  
<title>Welcome to nginx!</title>  
</head>  
<body bgcolor="white" text="black">  
<center><h1>Welcome to nginx! 192.168.232.134</h1></center>  
</body>  
</html>

134执行以下操作： vi /etc/keepalived/keepalived.conf

[plain] view plaincopyprint ?

! Configuration File for keepalived
global_defs {
notification_email {
#acassen@firewall.loc
#failover@firewall.loc
#sysadmin@firewall.loc
}
#notification_email_from Alexandre.Cassen@firewall.loc
#smtp_server 192.168.200.1
#smtp_connect_timeout 30
router_id LVS_DEVEL
}
vrrp_script chk_http_port {
script "</dev/tcp/127.0.0.1/8088"
interval 1
weight -2
}
vrrp_instance VI_1 {
state MASTER
interface eth2
virtual_router_id 51
priority 100
advert_int 1
authentication {
auth_type PASS
auth_pass 1111
}
virtual_ipaddress {
192.168.232.16
}
track_script {
chk_http_port
}
}

! Configuration File for keepalived

global_defs {
   notification_email {
     #acassen@firewall.loc
     #failover@firewall.loc
     #sysadmin@firewall.loc
   }
   #notification_email_from Alexandre.Cassen@firewall.loc
   #smtp_server 192.168.200.1
   #smtp_connect_timeout 30
   router_id LVS_DEVEL
}

vrrp_script chk_http_port {
    script "</dev/tcp/127.0.0.1/8088"
    interval 1
    weight -2
}

vrrp_instance VI_1 {
    state MASTER
    interface eth2
    virtual_router_id 51
    priority 100
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        192.168.232.16
    }
    track_script {
        chk_http_port
    }
}

135执行以下操作： vi /etc/keepalived/keepalived.conf

[plain] view plaincopyprint ?

! Configuration File for keepalived
global_defs {
notification_email {
#acassen@firewall.loc
#failover@firewall.loc
#sysadmin@firewall.loc
}
#notification_email_from Alexandre.Cassen@firewall.loc
#smtp_server 192.168.200.1
#smtp_connect_timeout 30
router_id LVS_DEVEL
}
vrrp_script chk_http_port {
script "</dev/tcp/127.0.0.1/8088"
interval 1
weight -2
}
vrrp_instance VI_1 {
state BACKUP
interface eth2
virtual_router_id 51
priority 99
advert_int 1
authentication {
auth_type PASS
auth_pass 1111
}
virtual_ipaddress {
192.168.232.16
}
track_script {
chk_http_port
}
}

! Configuration File for keepalived

global_defs {
   notification_email {
     #acassen@firewall.loc
     #failover@firewall.loc
     #sysadmin@firewall.loc
   }
   #notification_email_from Alexandre.Cassen@firewall.loc
   #smtp_server 192.168.200.1
   #smtp_connect_timeout 30
   router_id LVS_DEVEL
}

vrrp_script chk_http_port {
    script "</dev/tcp/127.0.0.1/8088"
    interval 1
    weight -2
}

vrrp_instance VI_1 {
    state BACKUP
    interface eth2
    virtual_router_id 51
    priority 99
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        192.168.232.16
    }
    track_script {
        chk_http_port
    }
}

Tips：
state 参数值：主的是MASTER、备用的是BACKUP priority 参数值： MASTER > BACKUP virtual_router_id：参数值要一样

测试测试：

两台测试机134\135均启动keepalived和nginx service keepalived restart service keepalived nginx
验证nginx启动正常：访问 master：http://192.168.232.134:8088/ 访问 backup: http://192.168.232.135:8088/
查看keepalived的日志信息：
134\135均打开日志信息方便查看keepalived动态： tail -f /var/log/messages
浏览器打开虚拟ip访问：http://192.168.232.16:8080/ ，此时显示IP为192.168.232.134

服务器层的双机热备（比如服务器宕机、keepalived宕了）测试：

kill 192.168.232.134（master) 的keepalived进程 killall keepalived 134的日志信息如下：

[plain] view plaincopyprint ?

Jun 11 18:03:10 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 192.168.232.16
Jun 11 18:03:15 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 192.168.232.16
Jun 11 19:30:44 localhost Keepalived: Terminating on signal
Jun 11 19:30:44 localhost Keepalived: Stopping Keepalived v1.2.2 (06/10,2014)
Jun 11 19:30:44 localhost Keepalived_vrrp: Terminating VRRP child process on signal
Jun 11 19:30:44 localhost Keepalived_healthcheckers: Terminating Healthchecker child process on signal

Jun 11 18:03:10 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 192.168.232.16
Jun 11 18:03:15 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 192.168.232.16
Jun 11 19:30:44 localhost Keepalived: Terminating on signal
Jun 11 19:30:44 localhost Keepalived: Stopping Keepalived v1.2.2 (06/10,2014)
Jun 11 19:30:44 localhost Keepalived_vrrp: Terminating VRRP child process on signal
Jun 11 19:30:44 localhost Keepalived_healthcheckers: Terminating Healthchecker child process on signal

135的日志信息如下：

[plain] view plaincopyprint ?

Jun 11 19:30:50 localhost Keepalived_vrrp: VRRP_Instance(VI_1) setting protocol VIPs.
Jun 11 19:30:50 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth2 for 192.168.232.16
Jun 11 19:30:50 localhost Keepalived_healthcheckers: Netlink reflector reports IP 192.168.232.16 added
Jun 11 19:30:55 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth2 for 192.168.232.16

Jun 11 19:30:50 localhost Keepalived_vrrp: VRRP_Instance(VI_1) setting protocol VIPs.
Jun 11 19:30:50 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth2 for 192.168.232.16
Jun 11 19:30:50 localhost Keepalived_healthcheckers: Netlink reflector reports IP 192.168.232.16 added
Jun 11 19:30:55 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth2 for 192.168.232.16

刷新http://192.168.232.16:8080/ ，此时显示IP为192.168.232.135。
再次启动192.168.232.134的keepalived进程，192.168.232.134会自动接管成为master，192.168.232.135自动转为backup，从测试结果看，备机能成功接管，已经实现了热备。

应用层（web）的双机热备（比如nginx进程被意外kill、web端口不通）试验：

关闭192.168.232.134（master) 的nginx服务： service nginx stop
134的日志信息如下：

[plain] view plaincopyprint ?

Jun 11 19:38:49 localhost Keepalived_vrrp: VRRP_Script(chk_http_port) failed
Jun 11 19:38:51 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Received higher prio advert
Jun 11 19:38:51 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Entering BACKUP STATE
Jun 11 19:38:51 localhost Keepalived_vrrp: VRRP_Instance(VI_1) removing protocol VIPs.
Jun 11 19:38:51 localhost Keepalived_healthcheckers: Netlink reflector reports IP 192.168.232.16 removed

Jun 11 19:38:49 localhost Keepalived_vrrp: VRRP_Script(chk_http_port) failed
Jun 11 19:38:51 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Received higher prio advert
Jun 11 19:38:51 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Entering BACKUP STATE
Jun 11 19:38:51 localhost Keepalived_vrrp: VRRP_Instance(VI_1) removing protocol VIPs.
Jun 11 19:38:51 localhost Keepalived_healthcheckers: Netlink reflector reports IP 192.168.232.16 removed

135的日志信息如下：

[plain] view plaincopyprint ?

Jun 11 19:38:52 localhost Keepalived_vrrp: VRRP_Instance(VI_1) forcing a new MASTER election
Jun 11 19:38:53 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Transition to MASTER STATE
Jun 11 19:38:54 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Entering MASTER STATE
Jun 11 19:38:54 localhost Keepalived_vrrp: VRRP_Instance(VI_1) setting protocol VIPs.
Jun 11 19:38:54 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth2 for 192.168.232.16
Jun 11 19:38:54 localhost Keepalived_healthcheckers: Netlink reflector reports IP 192.168.232.16 added
Jun 11 19:38:59 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth2 for 192.168.232.16

Jun 11 19:38:52 localhost Keepalived_vrrp: VRRP_Instance(VI_1) forcing a new MASTER election
Jun 11 19:38:53 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Transition to MASTER STATE
Jun 11 19:38:54 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Entering MASTER STATE
Jun 11 19:38:54 localhost Keepalived_vrrp: VRRP_Instance(VI_1) setting protocol VIPs.
Jun 11 19:38:54 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth2 for 192.168.232.16
Jun 11 19:38:54 localhost Keepalived_healthcheckers: Netlink reflector reports IP 192.168.232.16 added
Jun 11 19:38:59 localhost Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth2 for 192.168.232.16

刷新http://192.168.232.16:8080/ ，此时显示IP为192.168.232.135。
再次启动192.168.232.134的nginx进程，192.168.232.134会自动接管成为master，192.168.232.135自动转为backup，从测试结果看，备机能成功接管，已经实现了热备。

为什么主备的参数state都是MASTER，对的你没有看错确实要都设置成一样的，不然并不能实现我们想要的VIP漂浮的效果，我测试很久才发现的.state都设置成MASTER后，会根据priority的值大小竞争来决定谁是真正的MASTER，脚本检测也是在失败的时候会把权重减去相应的值，比如原来master（181）的priority=100，如果脚本检测到端口8088无法连接，就会priority-2=98，< S-B（150）的priority（99），此时 S-B（150）将竞争成为master，这样就实现了web应用的热备。

如果以上实验都没有问题了，那么就该nginx负载均衡的配置了，配置修改参见如下：http://blog.csdn.NET/e421083458/article/details/30086413

原文：http://www.cnblogs.com/kick/p/6274401.html

内容总结

以上是互联网集市为您收集整理的keepalived+nginx双机热备+负载均衡全部内容，希望文章能够帮你解决keepalived+nginx双机热备+负载均衡所遇到的程序开发问题。如果觉得互联网集市技术教程内容还不错，欢迎将互联网集市网站推荐给程序员好友。

内容备注

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容，请发送邮件至 gblab@vip.qq.com 举报，一经查实，本站将立刻删除。

内容手机端

扫描二维码推送至手机访问。

本文链接：https://qyyshop.com/info/1204211.html

来源：【匿名】

【上一篇】lvs负载均衡， ipvs的NAT模式，DR模式的实现，【下一篇】使用网络地址转换实现多服务器负载均衡

更多 ►

【keepalived+nginx双机热备+负载均衡】教程文章相关的互联网学习教程文章

keepalived+nginx双机热备+负载均衡【图】

LVS 负载均衡 ------ DR模式 + Keepalived【代码】【图】

文章目录一、keepalived（1）keepalived是什么（2）keepalived工作原理二、配置步骤：第一步：配置两台 DR第二步：配置第一台节点服务器 web1第三步：配置第二台节点服务器 web2第四步：客户端测试第五步：部署 keepalived第六步：实验结果验证一、keepalived ：（1）keepalived是什么keepalived是集群管理中保证集群高可用的一个服务软件，其功能类似于heartbeat，用来防止单点故障。1、keepalived的三个核心模块：core核心模块c...

lvs+keepalived实现高可用负载均衡

lvs+keepalived实现高可用负载均衡负载均衡集群的概念负载均衡是设计分布式系统架构必须要考虑的因素之一，它指的是通过调度分发的方式尽可能将“请求”、“访问”的压力负载平均分摊到集群中的各个节点，避免有些节点负载太高导致访问延迟，而有些节点负载很小导致资源浪费。这样，每个节点都可以承担一定的访问请求负载压力，并且可以实现访问请求在各节点之间的动态分配，以实现负载均衡，从而为企业提供更高性能，更加稳定的系...

Haproxy负载均衡+Keepalived高可用web群集【代码】

一、HAProxy 1.haproxy简介HAProxy 是一款提供高可用性、负载均衡以及基于TCP（第四层）和HTTP（第七层）应用的代理软件，支持虚拟主机，它是免费、快速并且可靠的一种解决方案。 HAProxy是一个使用C语言编写的自由及开放源代码软件HAProxy特别适用于那些负载特大的web站点，这些站点通常又需要会话保持或七层处理。HAProxy运行在当前的硬件上，完全可以支持数以万计的并发连接。并且它的运行模式使得它可以很简单安全的整合进您当...

Keepalived + LVS 高可用负载均衡集群部署【图】

Keepalived（高可用）通过在两台主、备调度器上实现Keepalived高可用解决调度器单点失败问题主、备调度器上配置LVS，正常情况下主调度器工作主调度器异常时，Keepalived启用备用调度器，保证了调度器的高可用调度器保证了后台服务的高可用 Keepalived机制把同一个IP一直分配给同一个Web服务器 650) this.width=650;" src="/upload/getfiles/default/2022/11/9/20221109024518749.jpg" t...

Keepalived + Nginx：负载均衡+高可用服务 --keepalived介绍及应用【代码】【图】

keepalived -- 综合架构高可用服务01. 内容说明:1) 负载均衡遗留知识点补充 2) 高可用服务的概念介绍 3) 部署安装高可用服务 4) 高可用服务配置文件参数说明 5) 高可用服务VRRP协议原理 6) 高可用服务常见问题(脑裂文件) 7) 高可用服务如何进行监控 8) 高可用服务实现双主配置 02. 回顾负载均衡企业实践应用https://www.cnblogs.com/moox/p/12775455.html03. 高可用服务介绍说明避免负载均衡服务出现单点问题设置主备负载均衡服务...

Nginx+Keepalived实现负载均衡高可用

Nginx+Keepalived实现负载均衡高可用一、环境5台虚拟机，分别是：1台测试机(192.168.2.83);2台nginx/keepalived(192.168.2.235/192.168.2.236);2台Web Servers(192.168.2.237/192.168.2.238);注：VIP设置为 192.168.2.229；二、安装配置Web Server由于Web Server的安装与配置非常简单，根据自己喜好，安装一个即可；比如：apache、nginx、tomcat等等。在此就不再详述；三、安装配置Nginxyum -y install gcc vim lrzsz pcre-devel k...

LVS+DR+apache+keepalived负载均衡【代码】

1、首先准备两台服务器、三台也可以我这里是两台IP:192.168.52.33IP:192.168.52.34VIP:192.168.52.1002、关闭防火墙systemctl stop firewalldsetenforce 03、安装keepalived,两台机器都需要安装yum -y install keepalived4、打开keepalived的配置文件，首先配置主的文件vim /etc/keepalived/keepalived.conf! Configuration File for keepalivedglobal_defs {notification_email {acassen@firewall.locfailover@firewall.locsysad...

Keepalived+HAproxy实现高可用负载均衡

总概： Keepalived是一个类似于layer3, 4 & 5交换机制的软件，也就是我们平时说的第3层、第4层和第5层交换。Keepalived的作用是检测web服务器的状态，如果有一台web服务器死机，或工作出现故障，Keepalived将检测到，并将有故障的web服务器从系统中剔除，当web服务器工作正常后Keepalived自动将web服务器加入到服务器群中，这些工作全部自动完成，不需要人工干涉，需要人工做的只是修复故障的web服务器 HAProxy提供高可用...

LVS+Keepalived负载均衡高可用如此简单？【代码】【图】

今天简单写下lvs+keepalive实现负载均衡和高可用的功能，仅供参考！关于它们的详细介绍这里就不描述了，大家可以自行搜索下！ lvs+keepalived网络拓扑图： 650) this.width=650;" title="lvs+keepalived.jpg" src="/upload/getfiles/default/2022/11/14/20221114065921745.jpg" />一、准备一个vip和4台虚拟机： vip:192.168.1.100向外提供服务的ip,一般是绑定域名的192.168.1.10LB1_master调度器IP192.168.1.13 LB2_slave调度器...

RedHat 7配置keepalived+LVS实现高可用的Web负载均衡【代码】【图】

上一篇博文中我们使用keepalived实现了haproxy的高可用，但keepalived问世之初却是为LVS而设计，与LVS高度整合，LVS与haproxy一样也是实现负载均衡，结合keepalived可以实现LVS的高可用架构，这一篇主要介绍RedHat 7配置keepalived+LVS实现高可用的Web负载均衡，架构图如下： 650) this.width=650;" title="架构图2.png" src="/upload/getfiles/default/2022/11/10/20221110031636093.jpg" />一、测试环境计算机名操作系统...

Keepalived+Nginx提供前端负载均衡+主从双机热备+自动切换【代码】

原文链接：http://unun.in/linux/156.html方案:采用两台Nginx服务器作为前端，提供静态web内容，分发web请求，一主一从，Keepalived实现状态监测，保证 Nginx正常对外提供服务，即主Nginx服务进程死掉之后，keepalived能够通过脚本或者程序检测机制，将网站的访问切换到从Nginx上来。后端的web应用服务器的监控由Nginx负责，keepalived只监控Nginx的健康状况。性能：大约是硬件负载均衡器的10%优势：虽然性能远弱于LVS+Keepalived...

LVS+keepalived做Mysql集群的负载均衡【代码】

LVS+keepalived做Mysql集群的负载均衡：注：1、LVS本身不对node做健康检查的，所以要借助keepalived2、根据配置当某node down掉会有几秒判断时间，这点请注意。负载均衡端：yum install ipvsadm keepalived ipset-devel注：keepalived的log在/var/log/message里vi /etc/keepalived/keepalived.conf! Configuration File for keepalivedglobal_defs {notification_email {@ming.com' title='br/>aa@ming.com' ref='nofollow'>br...

LVS+Keepalived实现高可用负载均衡

用LVS+Keepalived实现高可用负载均衡，简单来说就是由LVS提供负载均衡，keepalived通过对rs进行健康检查、对主备机(director)进行故障自动切换，实现高可用。1. LVS NAT模式配置准备三台服务器，一台director, 两台real serverdr1: 外网ip 192.168.75.130，内网ip 10.1.1.10两台real serverrs1: 内网ip 10.1.1.11rs2: 内网ip 10.1.1.12两台real server的内网网关设置为dr1的内网ip 10.1.1.10两个real server上都安装apache或者ngin...

LVS+Keepalived搭建MyCAT高可用负载均衡集群【代码】【图】

LVS+Keepalived 介绍LVSLVS是Linux Virtual Server的简写，意即Linux虚拟服务器，是一个虚拟的服务器集群系统。本项目在1998年5月由章文嵩博士成立，是中国国内最早出现的自由软件项目之一。目前有三种IP负载均衡技术（VS/NAT、VS/TUN和VS/DR），十种调度算法（rrr|wrr|lc|wlc|lblc|lblcr|dh|sh|sed|nq）。KeepalviedKeepalived在这里主要用作RealServer的健康状态检查以及Master主机和BackUP主机之间failover的实现下面，搭建基于...

负载均衡 - 相关标签

负载均衡策略负载均衡服务器负载均衡器负载均衡算法

负载均衡 - 最热教程

Nginx+Tomcat负载均衡之session问题 Nginx 负载均衡的Cache缓存批量清理的操...Docker：docker部署mysql5.7.21集群搭建...SqlServer横向扩展负载均衡终极利器Sql...laravelsession负载均衡 nginx+docker同一服务器上部署多个dock...4.CentOS7下双网卡实现负载均衡 win10 docker部署nginx对dotnetcore应用...Nginx做负载均衡无法加载css，js张宴f5...PHP实现负载均衡下的session共用功能

首页 / 负载均衡 / keepalived+nginx双机热备+负载均衡

keepalived+nginx双机热备+负载均衡

内容导读

内容图文

134\135两个主机配置虚拟IP

134\135两个主机安装keepalived和nginx

配置keeplived和nginx主机

测试测试：

服务器层的双机热备（比如服务器宕机、keepalived宕了）测试：

应用层（web）的双机热备（比如nginx进程被意外kill、web端口不通）试验：

内容总结

内容备注

内容手机端

【keepalived+nginx双机热备+负载均衡】教程文章相关的互联网学习教程文章

负载均衡 - 相关标签

负载均衡 - 最新教程

负载均衡 - 最热教程