On Thu, Oct 09, 2014 at 10:37:04PM +1300, Ivan Kurnosov wrote:
> > It's something I'd like to add also for the graceful shutdown, but for now
> we don't have an easy way to navigate through the idle connections. However
> something I was considering was to avoid keep-alive when serving a response
> over a saturated frontend or when the process is stopping. That way existing
> connections will fade out as new requests are sent over them. Do you think
> that would already be acceptable in your case ?
>
> What about `disable server app-servers/${name}`?
>
> I was just told that it will work, but I will only be able to check it
> tomorrow in the office.
If you disable all of your servers, users will end up with getting a 503 when
they want to send a new request.
> From my perspective - if it will, then the I miss
> the whole point of introducing of `set maxconn frontend <frontend_name> 0`
> in v1.5.0
It's in order to limit the amount of concurrent conns on a frontend. 0 is
just a value among other ones. This is important in a number of situations,
for example when you have a shared load balancer between many hosted customers.
You then want to limit one of them on the fly because it's eating all of
your resources.
Regards,
Willy
