Shulou(Shulou.com)06/03 Report--

1. Overview of nginx proxy 2, forward proxy of nginx 3, reverse proxy of nginx 4, load balancing of nginx 5, case: construction of nginx+lamp combined with nginx reverse proxy to realize separation of dynamic and static pages, and load balancing of php server 1. Concept of nginx proxy

Summary: nginx is a free, open source, high-performance HTTP server and reverse proxy server; it is also an IMAP, POP3, SMTP proxy server; (one less sentence here, sensitive words, please see the comments! )

Second, the forward agent of nginx

Analysis: analysis, please see the comments, there are sensitive words.

III. Reverse proxy of nginx

Layer 1: client, the client layer, the unit that issued the http request

The second layer: reverse proxy layer, agent layer, which is responsible for forwarding requests from client clients to the nodes of real servers in layer 3 (real server), and ensuring that real server nodes are not exposed in front of client.

The third layer: real server, the server layer, which is really responsible for handling requests from cleint clients, which is usually composed of multiple servers to form the effect of load balancing.

IV. Load balancing of nginx

Summary: nginx acts as a reverse proxy server. According to what rules does it request distribution? For unused project application scenarios, can the rules of distribution be controlled?

Implementation method:

Hardware load balancing: also known as hard load, such as F5 load balancing, it is relatively expensive and expensive, but the stability and security of data are well guaranteed. Companies such as China Mobile and China Unicom will choose hard load to operate.

Software load balancing: more companies will choose to use software load balancing because of the cost. Software load balancing is a message queue distribution mechanism implemented by existing technology combined with host hardware.

Nginx's load balancing algorithm:

1.weight polling (default): requests received are allocated to different back-end servers one by one in order. In this way, you can set a weight value (weight) for different back-end servers to adjust the allocation rate of requests on different servers; the larger the weight data, the greater the chance of being assigned to the request.

2.ip_hash: each request is matched according to the hash result of the ip of the originating client. Under this algorithm, a client with a fixed ip address will always access the same back-end server, which solves the problem of session sharing in the cluster deployment environment to some extent.

3.fair: intelligent adjustment scheduling algorithm, which dynamically allocates evenly according to the time from request processing to response of the back-end server. Servers with short response time and high efficiency have a high probability of allocation to requests, while servers with long response time and low efficiency allocate fewer requests. A scheduling algorithm that combines the advantages of the former two. But it should be noted that nginx does not support fair algorithm by default. If you want to use this scheduling algorithm, please install the upstream_fair module.

4.url_hash: assign requests according to the hash result of the accessed url. The url of each request will be directed to a server fixed at the back end, which can improve cache efficiency when nginx is used as a static server. It is also important to note that nginx does not support this scheduling algorithm by default. To use it, you need to install nginx's hash package.

Fifth, the case: combined with nginx reverse proxy to build nginx+lamp to achieve dynamic and static page separation and load balancing of php server

Case Topology:

Case environment:

System type IP address hostname memory required software Centos 7.4 1708 64bit192.168.100.101www.linuxfan.cn1Gnginx-1.12.2.tar.gzCentos 6.5 64bit192.168.100.150real1.linuxfan.cn1Ghttpd-2.2.17.tar.gz, cmake-2.8.6.tar.gz, mysql-5.5.22.tar.gz, libmcrypt-2.5.8.tar.gz, mcrypt-2.6.8.tar.gz, mhash-0.9.9.9.tar.gz, Php-5.3.28.tar.gz 、 ZendGuardLoader-php-5.3-linux-glibc23-x86_64.tar.gzCentos 6.5 64bit192.168.100.151real2.linuxfan.cn1Ghttpd-2.2.17.tar.gz 、 cmake-2.8.6.tar.gz 、 mysql-5.5.22.tar.gz 、 libmcrypt-2.5.8.tar.gz 、 mcrypt-2.6.8.tar.gz 、 mhash-0.9.9.9.tar.gz 、 php-5.3.28.tar.gz 、 ZendGuardLoader-php-5.3-linux-glibc23-x86_64.tar.gz case step: deploy lamp services for real1.linuxfan.cn nodes Deploy lamp service of real2.linuxfan.cn node; install nginx service of www.linuxfan.cn node; configure reverse proxy service of nginx node; client access test agent cluster; view log analysis access

Deploy lamp services for real1.linuxfan.cn nodes

[root@real1] # lslamp_install_publis-app-2015-07-16.tar.xz [root@real1 ~] # tar Jxvf lamp_install_publis-app-2015-07-16.tar.xz [root@real1 ~] # cd bin/ [root@real1 bin] #. / apache_install.sh &. / mysql_install.sh &. / mysql_config.sh &. / php_install.sh &. / php_config.sh &. / lamp_config.sh [ Root@real1 bin] # cd [root@real1 ~] # netstat-utpln | grep 80tcp 0 0:: 80: * LISTEN 50971/httpd [root@real1 ~] # netstat-utpln | grep 3306tcp 00 0.0.0.0 root@real1 3306 0.0.0.0 * LISTEN 6693/mysqld [root@real1 ~] # rm-rf / usr/local/httpd/htdocs/index.html [root@real1 ~] # vi / usr/local/httpd/htdocs/index.php

Deploy lamp services for real2.linuxfan.cn nodes

[root@real2] # lslamp_install_publis-app-2015-07-16.tar.xz [root@real2 ~] # tar Jxvf lamp_install_publis-app-2015-07-16.tar.xz [root@real2 ~] # cd bin/ [root@real2 bin] #. / apache_install.sh &. / mysql_install.sh &. / mysql_config.sh &. / php_install.sh &. / php_config.sh &. / lamp_config.sh [ Root@real2 bin] # cd [root@real2 ~] # netstat-utpln | grep 80tcp 0 0:: 80: * LISTEN 50971/httpd [root@real2 ~] # netstat-utpln | grep 3306tcp 00 0.0.0.0 root@real2 3306 0.0.0.0 * LISTEN 6693/mysqld [root@real2 ~] # rm-rf / usr/local/httpd/htdocs/index.html [root@real2 ~] # vi / usr/local/httpd/htdocs/index.php

Install the nginx service for the www.linuxfan.cn node

[root@www ~] # hostnamectl set-hostname www.linuxfan.cn [root@www ~] # hostnamewww.linuxfan.cn [root@www ~] # yum-y install pcre-devel zlib-devel [root@www] # useradd-M-s / sbin/nologin nginx [root@www ~] # tar zxvf nginx-1.12.2.tar.gz-C / usr/src/ [root@www ~] # cd / usr/src/nginx-1.12.2/ [root@www nginx-1.12. 2] #. / configure-- prefix=/usr/local/nginx-- user=nginx-- group=nginx-- with-http_stub_status_ module [root @ www nginx-1.12.2] # make & & make install [root@www nginx-1.12.2] # cd [root@www ~] # ln-s / usr/local/nginx/sbin/nginx / usr/local/sbin/ [root@www ~] # vi / usr/lib/systemd/system/nginx.service [Unit] Description=nginxapiAfter=network.target [ Service] Type=forkingPIDFile=/usr/local/nginx/logs/nginx.pidExecStart=/usr/local/nginx/sbin/nginxExecReload=kill-s HUP $(cat / usr/local/nginx/logs/nginx.pid) ExecStop=kill-s QUIT $(cat / usr/local/nginx/logs/nginx.pid) PrivateTmp= laser [install] WantedBy=multi-user.target [root@www ~] # systemctl start nginx [root@www ~] # systemctl enable nginx [root@www ~] # netstat-utpln | grep nginxtcp 00 0.0.0.0: 80 0.0.0.0 LISTEN 3538/nginx * master

Configure the reverse proxy service for the nginx node

[root@www ~] # vi / usr/local/nginx/conf/nginx.conf 34 upstream lamp_server {# # in the http region, 35 server 192.168.100.150 root html 80 weight=1; 36 server 192.168.100.150 root html 36 server 192.168.100.151 usr/local/nginx/conf/nginx.conf 80 weight=1; 37} 47 location / {48 root html 49 index index.html index.htm; 50} 51 location ~\. (asp | aspx | php | jsp | do) ${# # add 52 proxy_pass http://lamp_server; 53} [root@www ~] # systemctl stop nginx [root@www ~] # systemctl start nginx to the server area

View log analysis access

[root@www] # tail-3 / usr/local/nginx/logs/access.log 192.168.100.1-- [16/Jul/2018:17:01:34 + 0800] "GET / HTTP/1.1" 200612 "-" Mozilla/5.0 (Windows NT 10.0) WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 SE 2.x MetaSr 1.0 "192.168.100.1-- [16/Jul/2018:17:02:02 + 0800]" GET / index.php HTTP/1.1 "200797"-"Mozilla/5.0 (Windows NT 10.0) WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 SE 2.x MetaSr 1.0 "192.168.100.1-- [16/Jul/2018:17:02:11 + 0800]" GET / index.php HTTP/1.1 "200797"-"Mozilla/5.0 (Windows NT 10.0) WOW64) AppleWebKit/537.36 (KHTML Like Gecko) Chrome/58.0.3029.110 Safari/537.36 SE 2.x MetaSr 1.0 "[root@real1 ~] # tail-3 / usr/local/httpd/logs/access_log 192.168.100.102-- [16/Jul/2018:17:07:55 + 0800]" GET / index.php HTTP/1.0 "200 797192.168.100.102-- [16/Jul/2018:17:07:56 + 0800]" GET / index.php HTTP [16/Jul/2018:17:09:03 + 0800] "GET / index.php HTTP/1.0" 200797 [root@real2 ~] # tail-3 / usr/local/httpd/logs/access_log 192.168.100.102-[16/Jul/2018:17:07:56 + 0800] "GET / index.php HTTP/1.0" 200 797192.168.100.102-- [16 / Jul/2018:17:07:56 + 0800] "GET / index.php HTTP/1.0" 200 797192.168.100.102-[16/Jul/2018:17:09:12 + 0800] "GET / index.php HTTP/1.0" 200 797

Even if the list of cases is completed, check the log analysis!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.