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

This article to share with you is about nginx in the implementation of Load Balancer strategy what, Xiaobian think quite practical, so share to everyone to learn, I hope you can read this article after harvest, not to say much, follow Xiaobian to see it.

1. Polling (default)

Each request is assigned to a different backend server one by one in chronological order. If the backend server goes down, it can be automatically eliminated.

upstream backserver {

server 192.168.0.14;

server 192.168.0.15;

}

2. Assign weights

Specifies polling probability, weight proportional to access ratio, for uneven backend server performance.

upstream backserver {

server 192.168.0.14 weight=10;

server 192.168.0.15 weight=10;

}

3. IP binding ip_hash

Each request is allocated according to the hash result of the access ip, so that each visitor has fixed access to a backend server, which can solve the session problem.

upstream backserver {

ip_hash;

server 192.168.0.14:88;

server 192.168.0.15:80;

}

Fair (third party)

Requests are allocated according to the response time of the backend server, with priority given to the short response time.

upstream backserver {

server server1;

server server2;

fair;

}

url_hash (third party)

Distribute requests by hash result of access url, so that each url is directed to the same backend server, which is more effective when the backend server is cached.

upstream backserver {

server squid1:3128;

server squid2:3128;

hash $request_uri;

hash_method crc32;

}

Add to servers that require Load Balancer

proxy_pass http://backserver/;

upstream backserver{

ip_hash;

server 127.0.0.1:9090 down; (down means that the server in front of the single server will not participate in the load temporarily)

server 127.0.0.1:8080 weight=2; (weight defaults to 1.The greater the weight, the greater the load weight)

server 127.0.0.1:6060;

server 127.0.0.1: 7070 backup; (all other non-backup machines down or busy, request backup machines)

}

max_failures: The default number of failed requests allowed is 1. When the maximum number is exceeded, the error defined by proxy_next_upstream module is returned.

fail_timeout:max_times to pause after failure

The above are the strategies for implementing Load Balancer in nginx. Xiaobian believes that some knowledge points may be seen or used in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

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.