Nginx使用Keepalived部署web集群(高可用高性能負(fù)載均衡)實(shí)戰(zhàn)案例
前言
Keepalived 作為一個高性能的集群高可用解決方案。提供了集群節(jié)點(diǎn)心跳檢測、健康檢查以及故障切換的功能。原生支持 LVS 負(fù)載均衡集群。除了原生支持的LVS + Keepalived 外,現(xiàn)在 Nginx + Keepalived 也比較常用。接下來,我將詳細(xì)介紹 Nginx + Keepalived。
一、架構(gòu)設(shè)計(jì)
負(fù)載均衡方案系統(tǒng)架構(gòu)拓?fù)鋱D
二、環(huán)境準(zhǔn)備
| role | host | ip | software installed | OS |
|---|---|---|---|---|
| Nginx proxy、Keepalive MASTER | node01 | 192.168.5.11 | Nginx-1.10.0、keepalived | Centos 7.8 |
| Nginx proxy、Keepalive BACKUP | node02 | 192.168.5.12 | Nginx-1.10.0、keepalived | Centos 7.8 |
| nginx web server1 | node03 | 192.168.5.13 | Nginx-1.18.0 | Centos 7.8 |
| nginx web server1 | node04 | 192.168.5.14 | Nginx-1.18.0 | Centos 7.8 |
| Client | node05 | 192.168.5.15 | ---- | Centos 7.8 |
三、案例部署
配置 前端 Keepalived
---node01
[root@node01 ~]# vim /etc/keepalived/keepalived.conf
! 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.5.10
smtp_connect_timeout 30
router_id LVS_DEVEL1
}
vrrp_script check_nginx_service {
script "/etc/keepalived/check_web_server_keepalive.sh"
#script "killall -0 nginx"
interval 2
}
vrrp_instance VI_1 {
state MASTER
interface ens33
virtual_router_id 51
priority 200
advert_int 1
authentication {
auth_type PASS
auth_pass 1111
}
track_script {
check_nginx_service
}
virtual_ipaddress {
192.168.5.100
}
}
[root@node01 ~]# systemctl restart keepalived.service
---node02
! 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.5.10
smtp_connect_timeout 30
router_id LVS_DEVEL2
}
vrrp_script check_nginx_service {
script "/etc/keepalived/check_web_server_keepalive.sh"
#script "killall -0 nginx"
interval 2
}
vrrp_instance VI_1 {
state BACKUP
interface ens33
virtual_router_id 51
priority 100
advert_int 1
authentication {
auth_type PASS
auth_pass 1111
}
track_script {
check_nginx_service
}
virtual_ipaddress {
192.168.5.100
}
}
[root@node02 ~]# systemctl restart keepalived.service
配置 前端 Nginx 負(fù)載均衡
---node01
[root@node01 ~]# mv /etc/nginx/conf.d/default.conf{,.bak}
[root@node01 ~]# vim /etc/nginx/conf.d/vhost.conf
upstream nginx_keepalived_webservers {
server 192.168.5.13:80 weight=1;
server 192.168.5.14:80 weight=1;
}
server{
listen 80;
server_name wan.ngin_keepalived.org;
location / {
proxy_set_header X-Forwarded-For $remote_addr;
proxy_pass http://nginx_keepalived_webservers;
}
}
[root@node01 ~]# systemctl restart nginx
node02
[root@node02 ~]# mv /etc/nginx/conf.d/default.conf{,.bak}
[root@node02 ~]# vim /etc/nginx/conf.d/vhost.conf
upstream nginx_keepalived_webservers {
server 192.168.5.13:80 weight=1;
server 192.168.5.14:80 weight=1;
}
server{
listen 80;
server_name wan.ngin_keepalived.org;
location / {
proxy_set_header X-Forwarded-For $remote_addr;
proxy_pass http://nginx_keepalived_webservers;
}
}
[root@node02 ~]# systemctl restart nginx
配置前端 Nginx監(jiān)控腳本
---node01
[root@node01 ~]# vim /etc/keepalived/check_web_server_keepalive.sh
#!/bin/bash
http_status=`ps -C nginx --no-header | wc -l`
if [ $http_status -eq 0 ];then
systemctl start nginx
sleep 3
if [ `ps -C nginx --no-header | wc -l` -eq 0 ]
then
systemctl stop keepalived
fi
fi
[root@node02 ~]# vim /etc/keepalived/check_web_server_keepalive.sh
#!/bin/bash
http_status=`ps -C nginx --no-header | wc -l`
if [ $http_status -eq 0 ];then
systemctl start nginx
sleep 3
if [ `ps -C nginx --no-header | wc -l` -eq 0 ]
then
systemctl stop keepalived
fi
fi
配置后端 web 服務(wù)
---node03 [root@node03 ~]# yum install nginx-1.18.0-1.el7.ngx.x86_64.rpm -y [root@node03 ~]# echo "`hostname -I` web test page..." > /usr/share/nginx/html/index.html [root@node03 ~]# systemctl enable --now nginx ----node04 [root@node04 ~]# yum install nginx-1.18.0-1.el7.ngx.x86_64.rpm -y [root@node04 ~]# echo "`hostname -I` web test page..." > /usr/share/nginx/html/index.html [root@node04 ~]# systemctl enable --now nginx
客戶端訪問 VIP
實(shí)現(xiàn) Web 服務(wù)負(fù)載均衡 !
四、測試
node05 添加hosts解析
1、Keepalived 健康檢查
檢測 VIP 訪問 Web 服務(wù)
模擬后端服務(wù)故障
[root@node04 ~]# systemctl stop nginx [root@node04 ~]# systemctl is-active nginx inactive
檢測 VIP 訪問 Web 服務(wù)
模擬后端服務(wù)故障恢復(fù)
[root@node04 ~]# systemctl start nginx [root@node04 ~]# systemctl is-active nginx active
檢測 VIP 訪問 Web 服務(wù)
注:Nginx upstream 模塊默認(rèn)支持對后端服務(wù)健康監(jiān)測,Haproxy 同樣也自帶這種功能!
2、Keepalived MASTER/BACKUP 切換
查看keeapalived VIP 地址狀況
node01
node02
模擬 Keepalived MASTER 故障
[root@node01 ~]# systemctl stop keepalived.service
node01
node02
web 服務(wù)訪問不受影響
模擬 Keepalived MASTER 故障恢復(fù)
[root@node01 ~]# systemctl start keepalived.service
node01
node02
實(shí)現(xiàn) keeapalived VIP 漂移 !
測試前端 Nginx 負(fù)載均衡服務(wù)器
node01
Nginx 服務(wù)異常后 自動啟動!
node02
Web 訪問不受影響
模擬node01 nginx 服務(wù)無法啟動
node01
node02
Web 訪問不受影響
到此這篇關(guān)于Nginx使用Keepalived部署web集群(高可用高性能負(fù)載均衡)實(shí)戰(zhàn)案例的文章就介紹到這了,更多相關(guān)Nginx使用Keepalived部署web集群內(nèi)容請搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!
相關(guān)文章
win11安裝wsl報(bào)錯之無法解析服務(wù)器的名稱或地址的問題及解決方法
項(xiàng)目開發(fā)中,需要用到wsl,因此根據(jù)wsl官方(WSL安裝教程)命令?wsl --install 進(jìn)行wsl的安裝,本文主要是記錄自己在安裝wsl中遇到的問題"無法解析服務(wù)器的名稱或地址"的解決辦法,感興趣的朋友一起看看吧2024-04-04
webpack啟動服務(wù)器和處理sourcemap的操作方法
Source Map源代碼地圖就是解決此類問題最好的辦法,從它的名字就能夠看出它的作用:映射轉(zhuǎn)換后的代碼與源代碼之間的關(guān)系,這篇文章主要介紹了webpack啟動服務(wù)器和處理sourcemap的操作方法,需要的朋友可以參考下2024-03-03
雙至強(qiáng)cpu 32g內(nèi)存服務(wù)器 做了陣列1更換一個壞的硬盤后,沒做陣列
更換掉壞硬盤后,系統(tǒng)重新認(rèn)出primary后,原來的主盤即失效,如果此時再將更換掉的舊盤插入系統(tǒng)就會造成,混亂,導(dǎo)致進(jìn)不入系統(tǒng),撥掉也無用2013-06-06
VPS主機(jī)快速搬家方法:邊打包邊傳輸邊解壓適合大中型論壇網(wǎng)站
本篇文章給大家分享如何在VPS主機(jī)之間快速搬家,一邊打包壓縮原主機(jī)上的文件,一邊傳輸文件數(shù)據(jù)到新的主機(jī)上,一邊在新的VPS主機(jī)上解壓文件,因?yàn)樗械牟僮鞫际窃赩PS主機(jī)上之間進(jìn)行,傳輸速度可以達(dá)到幾MB/s以上,特別適合一些大中型的論壇和網(wǎng)站搬家2017-07-07
自設(shè)代理服務(wù)器緩存圖片節(jié)省上網(wǎng)流量
用移動公司的手機(jī)上網(wǎng)套餐,用電腦通過手機(jī)上網(wǎng),這個相信已經(jīng)有一部分人在進(jìn)行了。怎樣節(jié)省流量,是一個大問題。2011-01-01

