Nginx configuration to achieve multiple server load balancing

Nginx load balancing server: IP: 192.168.0.4 (Nginx-Server)

Web Server List:

Web1: 192.168.0.5 (Nginx-Node1/Nginx-Web1)

Web2:192.168.0.7 (Nginx-Node2/Nginx-Web2)

Purpose: When users access Nginx-Server, they are load balanced to Web1 and Web2 servers through Nginx.

Nginx load balancing server nginx.conf

The configuration comments are as follows:

events
{
use epoll;
worker_connections 65535;
}
http
{
##Upstream load balancing, four scheduling algorithms##
#Scheduling algorithm 1: Polling. Each request is assigned to a different backend server one by one in chronological order.
#If a backend server goes down, the faulty system will be automatically removed so that user access is not affected
upstream webhost {
server 192.168.0.5:6666 ;
server 192.168.0.7:6666 ;
}
#Scheduling algorithm 2: weight. You can define weights based on machine configuration. The higher the weight, the greater the chance of being assigned.
upstream webhost {
server 192.168.0.5:6666 weight=2;
server 192.168.0.7:6666 weight=3;
}
#Scheduling algorithm 3: ip_hash. Each request is assigned according to the hash result of the access IP, so that visitors from the same IP address will access a fixed backend server.
#Effectively solves the session sharing problem of dynamic web pages
upstream webhost {
ip_hash;
server 192.168.0.5:6666 ;
server 192.168.0.7:6666 ;
}
#Scheduling algorithm 4: url_hash (need to install a third-party plug-in). This method allocates requests according to the hash result of the access URL.
#Directing each URL to the same backend server can further improve the efficiency of the backend cache server.
#Nginx itself does not support url_hash. If you need to use this scheduling algorithm, you must install the Nginx hash package
upstream webhost {
server 192.168.0.5:6666 ;
server 192.168.0.7:6666 ;
hash $request_uri;
}
#Scheduling algorithm 5: fair (need to install a third-party plug-in). This is a smarter load balancing algorithm than the above two.
#This algorithm can intelligently balance the load based on the page size and loading time, that is, distribute requests based on the response time of the backend server.
# Prioritize the short response time. Nginx itself does not support fair. If you need to use this scheduling algorithm, you must download Nginx's upstream_fair module

#Configuration of virtual host (using scheduling algorithm 3: ip_hash)
server
{
listen 80;
server_name mongo.demo.com;
# Enable reverse proxy for "/"
location / {
proxy_pass http://webhost;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
#The backend Web server can obtain the user's real IP through X-Forwarded-For
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
#The following are some reverse proxy configurations, optional.
proxy_set_header Host $host;
client_max_body_size 10m; #The maximum number of bytes of a single file allowed to be requested by the client
client_body_buffer_size 128k; #The maximum number of bytes that the buffer proxy buffers the client request,
proxy_connect_timeout 90; #Nginx connection timeout with the backend server (proxy connection timeout)
proxy_send_timeout 90; #Backend server data return time (proxy send timeout)
proxy_read_timeout 90; #After the connection is successful, the backend server response time (proxy reception timeout)
proxy_buffer_size 4k; #Set the buffer size of the proxy server (nginx) to save user header information
proxy_buffers 4 32k; #proxy_buffers buffer, the average web page size is set below 32k
proxy_busy_buffers_size 64k; #buffer size under high load (proxy_buffers*2)
proxy_temp_file_write_size 64k;
#Set the cache folder size. If it is larger than this value, it will be transferred from the upstream server.
}
}
}
Configure 192.168.0.4 (Nginx-Server)

Create a folder to store the configuration file

$ mkdir -p /opt/confs
$ vim /opt/confs/nginx.conf
events
{
use epoll;
worker_connections 65535;
}
http
{
upstream webhost {
ip_hash;
server 192.168.0.5:6666 ;
server 192.168.0.7:6666 ;
}
server
{
listen 80;
server_name mongo.demo.com;
location / {
proxy_pass http://webhost;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;
client_max_body_size 10m;
client_body_buffer_size 128k;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 4k;
proxy_buffers 4 32k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
}
}
}
Start the load balancing server 192.168.0.4 (Nginx-Server)

Configure 192.168.0.5 (Nginx-Node1/Nginx-Web1)

Create a folder to store web pages

$ mkdir -p /opt/html
$ vim /opt/html/index.html
The edited content is as follows:

The host is 192.168.0.5 - Node 1

Start 192.168.0.5 (Nginx-Node1/Nginx-Web1)

Configure 192.168.0.7 (Nginx-Node2/Nginx-Web2)

Create a folder to store web pages

$ mkdir -p /opt/html
$ vim /opt/html/index.html
The edited content is as follows:

The host is 192.168.0.7 - Node 2

Start 192.168.0.7 (Nginx-Node2/Nginx-Web2)

This is the end of this article about Nginx configuration to achieve load balancing of multiple servers. For more relevant Nginx configuration load balancing content, please search for previous articles on 123WORDPRESS.COM or continue to browse the following related articles. I hope everyone will support 123WORDPRESS.COM in the future!