Apache-Talk @lexa.ru 

Inet-Admins @info.east.ru 

Filmscanners @halftone.co.uk 

Security-alerts @yandex-team.ru 

nginx-ru @sysoev.ru 





     АРХИВ :: nginx-ru
Nginx-ru mailing list archive (nginx-ru@sysoev.ru)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Ограничение на число одн овременных соединений, но с постановкой лишних в очередь

Dmitry Koterov schrieb:
Как будто бы maxconn в haproxy тоже ограничивает число подключений на весь кластер, а не per-HTTP_HOST:

maxconn <number>
  Sets the maximum per-process number of concurrent connections to <number>. It

  is equivalent to the command-line argument "-n". Proxies will stop accepting
  connections when this limit is reached. The "ulimit-n" parameter is
  automatically adjusted according to this value. See also "ulimit-n".

наверное имелось введу параметр maxqueue из описания  backend'a

maxconn <maxconn>
 The "maxconn" parameter specifies the maximal number of concurrent
 connections that will be sent to this server. If the number of incoming
concurrent requests goes higher than this value, they will be queued, waiting for a connection to be released. This parameter is very important as it can
 save fragile servers from going down under extreme loads. If a "minconn"
parameter is specified, the limit becomes dynamic. The default value is "0" which means unlimited. See also the "minconn" and "maxqueue" parameters, and
 the backend's "fullconn" keyword.

maxqueue <maxqueue>
 The "maxqueue" parameter specifies the maximal number of connections which
 will wait in the queue for this server. If this limit is reached, next
 requests will be redispatched to other servers instead of indefinitely
 waiting to be served. This will break persistence but may allow people to
 quickly re-log in when the server they try to connect to is dying. The
 default value is "0" which means the queue is unlimited. See also the
 "maxconn" and "minconn" parameters.

nginx-ru mailing list


Copyright © Lexa Software, 1996-2009.