> 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. 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

On 9 October 2014 22:31, Willy Tarreau <[email protected]> wrote:

> Hi Ivan,
>
> On Thu, Oct 09, 2014 at 04:10:29PM +1300, Ivan Kurnosov wrote:
> > Since `haproxy v1.5.0` it was possible to temporarily stop
> reverse-proxying
> > traffic to frontends using
> >
> >     set maxconn frontend <frontend_name> 0
> >
> > command.
> >
> > I've noticed that if haproxy is configured to maintain keepalive
> > connections between hapxory and a client then said connections will
> > continue be served whereas the new ones will continue awaiting for
> > "un-pausing" a frontend.
> >
> > The question is: is it possible to terminate current keepalive
> connections
> > *gracefully* so that a client was required to establish new connections?
>
> 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 ?
>
> > I've only found `shutdown session` and `shutdown sessions` commands but
> > they are obviously not graceful at all.
>
> Absolutely.
>
> Willy
>
>


-- 
With best regards, Ivan Kurnosov

Reply via email to