nginx upstream 调度策略

之前一直使用nginx 的upstream，今天有个哥们问我，upstream的调动算法是什么，我说我还真没注意过，使用Haproxy的时候倒是注意过，回来一查，原来也是round－robin，下面是nginx 官方文档给出的说明：

This module provides simple load-balancing (round-robin and client IP) across backend servers.

Example:

upstream

 backend  {

  server

 backend1.example.com weight=
5
;

  server

 backend2.example.com:8080
;

  server

 unix:/tmp/backend3;

}

 
server

 {

  location

 / {

    proxy_pass

  http

://backend;

  }

}

轮询调度算法(Round-Robin Scheduling)

　　轮询调度算法的原理是每一次把来自用户的请求轮流分配给内部中的服务器，从1开始，直到N(内部服务器个数)，然后重新开始循环。

　　算法的优点是其简洁性，它无需记录当前所有连接的状态，所以它是一种无状态调度。

　　轮询调度算法流程

　　假设有一组服务器N台，S = {S1, S2, …, Sn}，一个指示变量i表示上一次选择的服务器ID。变量i被初始化为N-1。其算法如下：

j = i;

do

{

j = (j + 1) mod n;

i = j;

return Si;

} while (j != i);

return NULL;

当然nginx也不止round-robin 这一种策略还有ip_hash 一种，这种好处就是一个ip总是被转发同一server

ip_hash

syntax: ip_hash

default: none

context: upstream

This directive causes requests to be distributed between upstreams based on the IP-address of the client.
The key for the hash is the class-C network address of the client. This method guarantees that the client request will always be transferred to the same server. But if this server is considered inoperative, then the request of this client will be transferred to another server. This gives a high probability clients will always connect to the same server.

It is not possible to combine ip_hash and weight methods for connection distribution. If one of the servers must be removed for some time, you must mark that server as *down*.

For example:

upstream

 backend {

  ip_hash

;

  server

   backend1.example.com;

  server

   backend2.example.com;

  server

   backend3.example.com  down;

  server

   backend4.example.com;

}