2. 程式人生 > >Nginx+keepalived+tomcat+負載均衡+反向代理

Nginx+keepalived+tomcat+負載均衡+反向代理

阿新 • • 發佈：2018-11-03

需求說明

實現nginx的keepalived和負載均衡

環境說明

ip 伺服器型別
172.16.11.19 nginx負載均衡伺服器（master）
172.16.11.21 nginx負載均衡伺服器（backup）
172.16.11.18 tomcat
172.16.11.20 tomcat

①.關閉防火牆

[
 
[email protected] ~]# systemctl stop firewalld.service

②.關閉selinux

[[email protected] ~]# setenforce 0
[[email protected] ~]# sed -ri 's/^(SELINUX=).*/\1disabled/g' /etc/selinux/config

③.配置網路源

[[email protected] ~]# curl -o /etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-7.repo
[
 
[email protected] ~]# sed -i 's/$releasever/7/g' /etc/yum.repos.d/CentOS-Base.repo

操作步驟

  • 172.16.11.19

①.安裝nginx和keepalived

[[email protected] ~]# yum -y install epel-release
[[email protected] ~]# yum -y install nginx keepalived

②.配置nginx的歡迎主頁，用於區分兩個節點的nginx

[[email protected]
 
 ~]# cd /usr/share/nginx/html/
[[email protected] html]# mv index.html{,.bak}
[[email protected] html]# echo 'master' > index.html

③.啟動nginx服務測試nginx

[[email protected] ~]# systemctl start nginx
[[email protected] ~]# systemctl enable nginx
Created symlink from /etc/systemd/system/multi-user.target.wants/nginx.service to /usr/lib/systemd/system/nginx.service.
[[email protected] ~]# ss -antl
State      Recv-Q Send-Q Local Address:Port               Peer Address:Port              
LISTEN     0      128           *: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                       :::*

在這裡插入圖片描述

④.配置keepalived

[[email protected] ~]# cd /etc/keepalived/
[[email protected] keepalived]# cp keepalived.conf keepalived.conf.bak          //備份主配置檔案
[[email protected] keepalived]# vim keepalived.conf
! Configuration File for keepalived

global_defs {           //全域性配置
// keepalived 自帶的郵件提醒需要開啟 sendmail 服務。 建議用獨立的監控或第三方 SMTP
   router_id lb_01     //標識節點的字串，同區域網內唯一
}

vrrp_instance VI_1 {           //例項，定義虛擬路由
    state MASTER        //節點的初始狀態，主為master，備為backup
    interface eth0        //繫結虛擬ip的網路介面，必須與本地ip所在介面相同
    virtual_router_id 51           //虛擬路由id號，兩個節點必須一樣
    priority 100           //節點優先順序，master要比backup高
    advert_int 1        //兩個節點發送組播資訊間隔時間，主備需要設定相同的時間，預設為秒
    authentication {          //配置認證
        auth_type PASS             //PASS即為密碼認證
        auth_pass 1111          //設定密碼，可自定義
    }
    virtual_ipaddress {        //設定虛擬ip（VIP），兩個節點需要一樣
        172.16.11.200
    }
}

virtual_server 172.16.11.200 80 {         //虛擬伺服器配置
    delay_loop 6      //健康檢查的時間間隔
    lb_algo rr          //lvs排程演算法
    lb_kind NAT        //lvs模式
    persistence_timeout 50           //持久化超時時間，單位為秒
    protocol TCP               //OSI的四層協議，即網路層

    real_server 172.16.11.19 80 {         //真實處理請求的伺服器配置
        weight 1        //指定權重
        TCP_CHECK {
            connect_timeout 3            //連線超時時間
            nb_get_retry 3       //重試次數
            delay_before_retry 3         //在重試之前延遲多長時間
        }
    }
    real_server 172.16.11.21 80 {
        weight 1
        TCP_CHECK {
            connect_timeout 3
            nb_get_retry 3
            delay_before_retry 3
        }
    }

}

⑤.啟動keepalived

[[email protected] keepalived]# systemctl start keepalived.service 
[[email protected] keepalived]# systemctl enable keepalived.service 
Created symlink from /etc/systemd/system/multi-user.target.wants/keepalived.service to /usr/lib/systemd/system/keepalived.service.
  • 172.16.11.21

①.安裝nginx和keepalived

[[email protected] ~]# yum -y install epel-release
[[email protected] ~]# yum -y install nginx keepalived

②.配置nginx的歡迎主頁，用於區分兩個節點的nginx

[[email protected] ~]# cd /usr/share/nginx/html/
[[email protected] html]# mv index.html{,.bak}
[[email protected] html]# echo 'backup' > index.html

③.啟動nginx服務測試nginx

[[email protected] ~]# systemctl start nginx
[[email protected] ~]# systemctl enable nginx
Created symlink from /etc/systemd/system/multi-user.target.wants/nginx.service to /usr/lib/systemd/system/nginx.service.
[[email protected] ~]# ss -antl
State      Recv-Q Send-Q Local Address:Port               Peer Address:Port              
LISTEN     0      128           *: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                       :::*

在這裡插入圖片描述
④.配置keepalived

[[email protected] ~]# cd /etc/keepalived/
[[email protected] keepalived]# cp keepalived.conf keepalived.conf.bak          //備份主配置檔案
[[email protected] keepalived]# vim keepalived.conf
! Configuration File for keepalived

global_defs {           //全域性配置
// keepalived 自帶的郵件提醒需要開啟 sendmail 服務。 建議用獨立的監控或第三方 SMTP
   router_id lb_02    //標識節點的字串，同區域網內唯一
}

vrrp_instance VI_1 {           //例項，定義虛擬路由
    state BACKUP        //節點的初始狀態，主為master，備為backup
    interface ens33        //繫結虛擬ip的網路介面，必須與本地ip所在介面相同
    virtual_router_id 51           //虛擬路由id號，兩個節點必須一樣
    priority 90           //節點優先順序，master要比backup高
    advert_int 1        //兩個節點發送組播資訊間隔時間，主備需要設定相同的時間，預設為秒
    authentication {          //配置認證
        auth_type PASS             //PASS即為密碼認證
        auth_pass 1111          //設定密碼，可自定義
    }
    virtual_ipaddress {        //設定虛擬ip（VIP），兩個節點需要一樣
        172.16.11.200
    }
}

virtual_server 172.16.11.200 80 {         //虛擬伺服器配置
    delay_loop 6      //健康檢查的時間間隔
    lb_algo rr          //lvs排程演算法
    lb_kind NAT        //lvs模式
    persistence_timeout 50           //持久化超時時間，單位為秒
    protocol TCP               //OSI的四層協議，即網路層

    real_server 172.16.11.19 80 {         //真實處理請求的伺服器配置
        weight 1        //指定權重
        TCP_CHECK {
            connect_timeout 3            //連線超時時間
            nb_get_retry 3       //重試次數
            delay_before_retry 3         //在重試之前延遲多長時間
        }
    }
    real_server 172.16.11.21 80 {
        weight 1
        TCP_CHECK {
            connect_timeout 3
            nb_get_retry 3
            delay_before_retry 3
        }
    }

}

⑤.啟動keepalived

[[email protected] keepalived]# systemctl start keepalived.service 
[[email protected] keepalived]# systemctl enable keepalived.service 
Created symlink from /etc/systemd/system/multi-user.target.wants/keepalived.service to /usr/lib/systemd/system/keepalived.service.

分別在兩臺機器上檢視ip

  • 172.16.11.19
[[email protected] keepalived]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:35:dd:b8 brd ff:ff:ff:ff:ff:ff
    inet 172.16.11.19/24 brd 172.16.11.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 172.16.11.200/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe35:ddb8/64 scope link 
       valid_lft forever preferred_lft forever
  • 172.16.11.21
[[email protected] keepalived]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:72:aa:10 brd ff:ff:ff:ff:ff:ff
    inet 172.16.11.21/24 brd 172.16.11.255 scope global ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::c6eb:d9f9:32e9:f3df/64 scope link 
       valid_lft forever preferred_lft forever

可以看出來，在主master伺服器上，出現了虛擬ip，這時候停掉主master伺服器的nginx和keepalived，再來看看

  • 172.16.11.19
[[email protected] keepalived]# systemctl stop nginx
[[email protected] keepalived]# systemctl stop keepalived.service 
[[email protected] keepalived]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:35:dd:b8 brd ff:ff:ff:ff:ff:ff
    inet 172.16.11.19/24 brd 172.16.11.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe35:ddb8/64 scope link 
       valid_lft forever preferred_lft forever
  • 172.16.11.21
[[email protected] keepalived]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:72:aa:10 brd ff:ff:ff:ff:ff:ff
    inet 172.16.11.21/24 brd 172.16.11.255 scope global ens33
       valid_lft forever preferred_lft forever
    inet 172.16.11.200/32 scope global ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::c6eb:d9f9:32e9:f3df/64 scope link 
       valid_lft forever preferred_lft forever

可以看到虛擬ip漂移到了備backup伺服器上面，現在備backup伺服器成為了主master

為了防止出現主master伺服器nginx掛了，然後keeplived沒有停掉，導致出現虛擬ip還是在掛掉的nginx伺服器上面，但是因為nginx掛掉了無法訪問後端伺服器，需要寫一個指令碼來監控nginx的狀態並自動控制keeplived，這個指令碼放在主master伺服器上面，

  • 172.16.11.19
    ①.寫監控nginx的指令碼
[[email protected] ~]# mkdir /etc/keepalived/scripts
[[email protected] ~]# cd /etc/keepalived/scripts
[[email protected] scripts]# vim check_n.sh
#!/bin/bash

status=`ps -ef | grep '\bnginx\b' | grep -Ev "grep|${0}" | wc -l`

if [ $status -eq 0 ];then
     systemctl stop keepalived
fi
[[email protected] scripts]# chmod +x check_n.sh

②.修改master的配置檔案,在global_defs全域性配置後新增

[[email protected] scripts]# vim /etc/keepalived/keepalived.conf
vrrp_script nginx_check {
    script "/etc/keeplived/scripts/check_n.sh"         //要執行的指令碼的路徑
    interval 1          //執行指令碼間隔時間，單位為秒，預設1秒
    weight -20     //調整優先順序
}

然後寫一個指令碼，通過這個指令碼來使當主master伺服器的nginx掛掉，然後backup變為master的時候傳送郵件，並自動啟動nginx，當原master伺服器被修復以後，原backup伺服器恢復原樣，並停掉nginx.（注：只能有一邊的nginx啟動才能通過虛擬ip訪問，不然兩邊都啟動nginx，即使你的虛擬ip在master上也訪問不到）

發郵件的伺服器上面需要安裝mailx
yum -y install mailx

  • 172.16.11.19

①.在master上編寫指令碼

[[email protected] scripts]# vim notify.sh
#!/bin/bash

VIP=$2
sendmail (){
        subject="${VIP} ip address drift"        content="`date +'%F-%H%M%S'`:`ip a | grep eth0 | grep inet | head -1 | awk -F '[ /]+' '{print $3}'` change to master"
        echo $conter | mail -s "$subject" [email protected]
}

case "$1" in
  master)
            systemctl start nginx

;;
  backup)        
            systemctl stop nginx

;;
  *)
        echo "Usage:$0 master|backup $VIP"
;;
esac
~     
[[email protected] scripts]# chmod +x notify.sh

②.修改配置檔案，在vrrp_instance裡面最後新增

[[email protected] scripts]# vim /etc/keepalived/keepalived.conf
vrrp_instance VI_1 {
......
    track_script {
        nginx_check
    }
    notify_master "/etc/keeplived/scripts/notify.sh master 172.16.11.200"
    notify_backup "/etc/keeplived/scripts/notify.sh backup 172.16.11.200"

}
  • 172.16.11.21

backup無需檢測nginx是否正常，當升級為master時啟動nginx，當降級為backup時關閉

①.在backup上編寫指令碼

[[email protected] ~]# mkdir /etc/keepalived/scripts
[[email protected] ~]# cd /etc/keepalived/scripts
[[email protected] scripts]# vim notify.sh
#!/bin/bash

VIP=$2
sendmail (){
        subject="${VIP} ip address drift"
        content="`date +'%F-%H%M%S'`:`ip a | grep ens33 | grep inet | head -1 | awk -F '[ /]+' '{print $3}'` change to master"
        echo $conter | mail -s "$subject" [email protected]
}

case "$1" in
            systemctl start nginx
;;
  backup)
            systemctl stop nginx
;;
  *)
        echo "Usage:$0 master|backup $VIP"
;;
esac
[[email protected] scripts]# chmod +X notify.sh 
[[email protected] scripts]# yum -y install mailx      //安裝郵箱命令

②.修改配置檔案，在vrrp_instance裡面最後新增

[[email protected] scripts]# vim /etc/keepalived/keepalived.conf
vrrp_instance VI_1 {
......

    notify_master "/etc/keeplived/scripts/notify.sh master 172.16.11.200"
    notify_backup "/etc/keeplived/scripts/notify.sh backup 172.16.11.200"

}

到這裡就可以nginx的keepalived就配置完成了，接下來就可以來配置負載均衡和反向代理了

  • 172.16.11.18
    ①.安裝jdk開發環境
[[email protected] ~]# yum -y install java-1.8.0-openjdk java-1.8.0-openjdk-devel

②.到官網下載tomcat包

 [[email protected] ~]# wget https://archive.apache.org/dist/tomcat/tomcat-9/v9.0.8/bin/apache-tomcat-9.0.8.tar.gz

③.解壓tomcat，並配置網頁

[[email protected] ~]# tar -xf apache-tomcat-9.0.8.tar.gz -C /usr/local/
[[email protected] ~]# ln -s /usr/local/apache-tomcat-9.0.8/ /usr/local/tomcat
[[email protected] tomcat]# cd /usr/local/tomcat/webapps/
[[email protected] webapps]# mkdir test
[[email protected] webapps]# vim test/index.jsp
<html>
<head>
        <title>test page</title>
</head>
<body>
<       %
            out.println("Hellow World");
        %>
</body>
</html>
[[email protected] webapps]# /usr/local/tomcat/bin/catalina.sh start
  • 172.16.11.20
    ①.安裝jdk開發環境
[[email protected] ~]# yum -y install java-1.8.0-openjdk java-1.8.0-openjdk-devel

②.到官網下載tomcat包

 [[email protected] ~]# wget https://archive.apache.org/dist/tomcat/tomcat-9/v9.0.8/bin/apache-tomcat-9.0.8.tar.gz

③.解壓tomcat，並配置網頁

[[email protected] ~]# tar -xf apache-tomcat-9.0.8.tar.gz -C /usr/local/
[[email protected] ~]# ln -s /usr/local/apache-tomcat-9.0.8/ /usr/local/tomcat
[[email protected] tomcat]# cd /usr/local/tomcat/webapps/
[[email protected] webapps]# mkdir test
[[email protected] webapps]# vim test/index.jsp
<html>
<head>
        <title>test page</title>
</head>
<body>
<       %
            out.println("Hellow World too");
        %>
</body>
</html>
[[email protected] webapps]# /usr/local/tomcat/bin/catalina.sh start

在nginx上配置負載均衡和反向代理

  • 172.16.11.19
[[email protected] scripts]# vim /etc/nginx/nginx.conf
    upstream web.com {                    //新增在http段
        server 172.16.11.18:8080;
        server 172.16.11.20:8080
    }
        location ~ \.jsp {                        //新增在server段
            proxy_pass http://web.com;
        }
  • 172.16.11.21
[[email protected] scripts]# vim /etc/nginx/nginx.conf
    upstream web.com {                    //新增在http段
        server 172.16.11.18:8080;
        server 172.16.11.20:8080;
    }
        location ~ \.jsp {                        //新增在server段
            proxy_pass http://web.com;
        }

測試

當master的nginx和keepalived都啟動的時候，訪問虛擬ip

  • 172.16.11.19
[[email protected] ~]# systemctl start nginx
[[email protected] ~]# systemctl start keepalived.service 
[[email protected] ~]# ip add show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:35:dd:b8 brd ff:ff:ff:ff:ff:ff
    inet 172.16.11.19/24 brd 172.16.11.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 172.16.11.200/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe35:ddb8/64 scope link 
       valid_lft forever preferred_lft forever

在這裡插入圖片描述
在這裡插入圖片描述

可以看到訪問到後端的tomcat伺服器上面並實現了負載均衡

然後停掉master的nginx，可以看到keepalived也自動停掉了，並且原backup成為了master，虛擬ip漂移，也傳送了郵件

  • 172.16.11.19
[[email protected] ~]# systemctl stop nginx
[[email protected] ~]# systemctl status keepalived.service 
● keepalived.service - LVS and VRRP High Availability Monitor
   Loaded: loaded (/usr/lib/systemd/system/keepalived.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Thu 2018-11-01 23:59:10 CST; 17s ago
  Process: 40968 ExecStart=/usr/sbin/keepalived $KEEPALIVED_OPTIONS (code=exited, status=0/SUCCESS)
 Main PID: 40969 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/keepalived.service

Nov 01 23:49:57 lizihan Keepalived_vrrp[40971]: VRRP_Instance(VI_1) Sending/qu...0
Nov 01 23:49:57 lizihan Keepalived_vrrp[40971]: Sending gratuitous ARP on eth0...0
Nov 01 23:49:57 lizihan Keepalived_vrrp[40971]: Sending gratuitous ARP on eth0...0
Nov 01 23:49:57 lizihan Keepalived_vrrp[40971]: Sending gratuitous ARP on eth0...0
Nov 01 23:49:57 lizihan Keepalived_vrrp[40971]: Sending gratuitous ARP on eth0...0
Nov 01 23:59:09 lizihan Keepalived[40969]: Stopping
Nov 01 23:59:09 lizihan systemd[1]: Stopping LVS and VRRP High Availability M.....
Nov 01 23:59:09 lizihan Keepalived_vrrp[40971]: VRRP_Instance(VI_1) sent 0 pri...y
Nov 01 23:59:09 lizihan Keepalived_vrrp[40971]: VRRP_Instance(VI_1) removing p....
Nov 01 23:59:10 lizihan systemd[1]: Stopped LVS and VRRP High Availability Mo...r.
Hint: Some lines were ellipsized, use -l to show in full.
[[email protected] ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:35:dd:b8 brd ff:ff:ff:ff:ff:ff
    inet 172.16.11.19/24 brd 172.16.11.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe35:ddb8/64 scope link 
       valid_lft forever preferred_lft forever
  • 172.16.11.21
[[email protected] ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:72:aa:10 brd ff:ff:ff:ff:ff:ff
    inet 172.16.11.21/24 brd 172.16.11.255 scope global ens33
       valid_lft forever preferred_lft forever
    inet 172.16.11.200/32 scope global ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::c6eb:d9f9:32e9:f3df/64 scope link 
       valid_lft forever preferred_lft forever

在這裡插入圖片描述

這時候再訪問虛擬ip
在這裡插入圖片描述

在這裡插入圖片描述

相關推薦

Nginx+keepalived+tomcat+負載均衡+反向代理

需求說明 實現nginx的keepalived和負載均衡 環境說明 ip 伺服器型別 172.16.11.19 nginx負載均衡伺服器（master）

keepalived+nginx負載均衡反向代理

nginx-proxy llinuxkeepalived配置 vrrp_script chk_http_port { script "/root/check_nginx_pid.sh" interval 2 #（檢測腳本執行的間隔） w

Nginx學習總結（10）——Nginx前後端分離將多個請求轉發到多個Tomcat，負載均衡反向代理

一、談談“渲染” 相信好多人都挺聽過“渲染”這個詞，但不清楚它是什麼意思？前端開發以為這是後端的活兒，後端開發以為是前端的事兒，推著推著就不了了之。其實渲染很簡單，不說概念，直接舉例： 1、 後端渲染：以JSP為例，可以分成三步 a、編寫標籤或Java程式碼（可以稱之為模板

Nginx 負載均衡反向代理

一、叢集介紹以及常用叢集硬體知識介紹及選型 1、負載均衡以及高可用叢集的作用1）、負載均衡叢集的作用：a、分擔使用者訪問請求及資料流量（負載均衡）b、保持業務連續性，即 7x24 小時服務（高可用性）c、應用於 web 業務及資料庫從庫等伺服器的業務。負載均衡叢集典型的開源軟體：LVS、Nginx、Hap

nginx做為web容器部署靜態資源以及做負載均衡反向代理實現

需求：  此時前臺開發完成打包生成靜態資原始檔，要做到以下方面： 　　使用nginx部署靜態資源，同時nginx要實現埠轉發，隱藏真實後臺地址，同時後臺需要做一個負載均衡。 　　localhost:7001是前臺地址，訪問後臺localhost:7001/backend&nbs

Nginx HTTP負載均衡/反向代理的相關引數測試

測試目的 （1）弄清楚HTTP Upstream 模組中Server指令的max_fails與fail_timeout參 數的關係、它們對後端伺服器健康情況的檢查起到了什麼作用、它們的取值對Http proxy模組中的其它指令是否有直接或間接的影響等…… （2）測試

負載均衡,反向代理，叢集解釋

作為開發人員程式碼寫完了還要會部署專案，部署專案然後得接觸到很多跟開發不大有關的技術，下面列出叢集，負載均衡，反向代理等定義解釋。執行緒這塊以後接觸後再新增， 負載均衡：軟體負載均衡（Nginx），硬體負載均衡（f5） 還有其他的。 web最開始請求整個流程，使用者輸入網址，然後資原始檔載入

python flask nginx keepalived 實現負載均衡

最近在部署一個flask服務，要了兩臺伺服器嘗試了一下負載均衡 環境：Centos，python3,flask,nginx,keepalived， 確保上述包安裝成功 首先實現nginx的負載均衡140.143.66.123:90是我的主機，埠90是因為flask服務監聽的是90埠，權重

Linux配置Nginx＋Tomcat負載均衡

14. func tomcat att 模塊 error 新解 c++環境 make tar -zxvf nginx-1.14.2.tar.gz -C /usr/local 一、Linux配置Nginx 一、下載Nginx 　　方式1：從http://nginx.org/e

配置apache和nginx的tomcat負載均衡

概述   本篇文章主要介紹apache和nginx的相關配置，tomcat的相關安裝配置我在前面有寫過一篇，詳細介紹通過兩種配置方法配置nginx。 tomcat配置參考：http://www.cnblogs.com/chenmh/p/5048893.html apache配置  原始碼安裝

nginx配置tomcat負載均衡+nginx伺服器+apache後端伺服器

nginx配置tomcat負載均衡 nginx可以作為Web前置機，將客戶請求按照一定演算法合理分配給後置的tomcat應用伺服器，從而達到均衡目的。當然如果應用使用了session會話，後 置的tomcat應用還要保證session共享才能達到應用叢集效果。本文不討論tomcat的叢集問題，重點討論n

負載均衡反向代理模式優點及缺點

通代理方式是代理內部網路使用者訪問internet上伺服器的連線請求，客戶端必須指定代理伺服器,並將本來要直接傳送到internet上伺服器的連線請求傳送給代理伺服器處理。 反向代理（Reverse Proxy）方式是指以代理伺服器來接受internet上的連線請求，

Nginx和Tomcat負載均衡實現session共享

    以前的專案使用Nginx作為反向代理實現了多個Tomcat的負載均衡，為了實現多個Tomcat之間的session共享，使用了開源的Memcached-Session-Manager框架。     此框架的優勢：          1、支援Tomcat6和Tomca

【Nginx】nginx反向代理與tomcat負載均衡

前言         nginx反向代理大大節省了伺服器開支，通過配置多個虛擬主機，使多個服務共同的使用虛擬的80埠。 首先，某個伺服器上有多個tomcat服務，分別佔用一個埠。先看配置檔案。 tomcat服務1 upstream sina{ server 192

基於nginx和tengine的tcp反向代理，負載均衡 安裝和配置

zip http 端口 arc -s pro 進入 iteye obj 先下載nginx_tcp_proxy_module模塊。 wget https://github.com/yaoweibin/nginx_tcp_proxy_module/archive/mast

公司nginx keepalived tomcat cxf 搭建高可用負載均衡實戰系列1- keepalived安裝配置

技術分享 cnblogs start ges idt def auth div .cn 1，ip說明 vip 10.50.13.67 server1 10.50.13.68 server2 10.50.13.140 2

nginx實戰（四）反向代理配置緩存及負載均衡

cer zone ofo domain 針對 臨時文件 地址 ike ipv6 前言 反向代理，是指用戶通過同一服務器訪問服務器後端各被代理服務器的訪問方式。（詳見百度百科 https://baike.baidu.com/item/反向代理/7793488 ）? nginx

Nginx+Keepalived+Tomcat+MySQL負載均衡& 通過nginx排程器訪問Tom

目錄第一部分 環境準備第二部分 部署排程器—搭建Nginx+Keepalived（雙機熱備）第三部分 部署伺服器池—搭建Tomcat第四部分 搭建Mysql資料庫第五部分 案例應用 第一部分 環境準備 一：Nginx+keepalived伺服器兩臺（排程器，雙機熱備）系統：Linux—CentOS7.4I

nginx的虛擬主機、反向代理、負載均衡的應用

一、tomcat服務的準備（tomcat和nginx安裝在同一臺的虛擬機器裡面，而tomcat使用8081和9080兩個埠啟動，nginx使用80埠） 1、nginx和tomcat的安裝位置：  （注意：在同一臺虛擬機器裡面開兩個tomcat伺服器，啟動埠分別為8081和

Nginx服務搭建負載均衡，反向代理，快取加速，訪問分散式檔案系統高可用

主配置檔案如下：[[email protected]~]#vim /usr/local/nginx/conf/nginx.conf server{ listen 8099               //埠號 location / {      autoindex on;      autoinde