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

It is believed that many inexperienced people have no idea about how to achieve load balancing in Nginx. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

Upstream supports four load balancing scheduling algorithms:

A) polling (default): each request is assigned to different back-end servers one by one in chronological order

B) ip_hash: each request is allocated according to the hash result of accessing IP, and the same IP client accesses a back-end server on a fixed basis. The session problem can be solved by ensuring that requests from the same ip are sent to a fixed machine.

C) url_hash: allocate requests according to the hash results of accessing url, so that each url is directed to the same back-end server. Efficiency when the background server is cached.

D) fair: this is a more intelligent load balancing algorithm than the above two. This algorithm can intelligently balance the load according to the page size and loading time, that is, the request can be allocated according to the response time of the back-end server, and the priority allocation of short response time. Nginx itself does not support fair, and if you need to use this scheduling algorithm, you must download the upstream_fair module of Nginx.

1. Default rotation training

Open the nginx configuration file

[root@master ~] # vi / etc/nginx/conf.d/default.conf

Write rotation training configuration

# set load balancer server list upstream roundrobin {# backend server access rules server 192.168.1.115 server1 server 8080 weight=1; # server1 server 192.168.1.131server 8081 weight=1; # server1 server 192.168.1.94 Vera 8090 weight=1; # server3} server {listen 80; server_name 192.168.1.131; location / {proxy_pass Server}}

After the configuration is completed

/ / check whether the nginx configuration is correct nginx-t / / reload the nginx configuration service nginx reload

When accessing http://192.168.131, the request is loaded to port 8080 of 192.168.1.115, port 8080 of 192.168.1.115, and port 8080 of 192.168.1.115. The weight of the load is determined by weight, which defaults to 1. The greater the weight, the greater the weight.

2. Based on hash

# set load balancer server list upstream roundrobin {# backend server access rules ip_hash; # add parameters to support hash server 192.168.1.115 weight=1; # server1 server 192.168.1.131ip_hash; 8080 weight=1; # server1 server 192.168.1.94 ip_hash; 8090 weight=1; # server3} server {listen 80; server_name 192.168.1.131; location / {proxy_pass Server}}

Set the status of the backend load balancer server

Down, which means that the current server does not participate in load balancing for the time being.

Backup, reserved backup machine. The backup machine is requested only when all other non-backup machines are malfunctioning or busy, so this machine is the least stressful.

Note: backup and ip_hash cannot be configured at the same time. Because ip_hash can only access the same server, backup requests backup machines only when all the servers participating in load balancer fail. When all load balancing servers fail, ip_hash 's will no longer be able to request.

# set load balancer server list upstream roundrobin {# backend server access rules server 192.168.1.115 server1 server 8080 weight=1; # server1 server 192.168.1.131server 8080 down; # server2 do not participate in load server 192.168.1.94 server 8090 backup; # server3 backup machine} server {listen 80; server_name 192.168.1.131; location / {proxy_pass server }} after reading the above, have you mastered how to achieve load balancing in Nginx? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

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.