Hi Willy,
> > Seems that it's considered an expected behavior to consider
> > optimistically the server as UP
> > when leaving MAINT mode, even if the L4 health checks are not completed
> > yet.
> Normally using the existing API you could forcefully
> mark the server's check as down using
On Tue, May 23, 2023 at 11:21:28AM +0200, Thomas Pedoussaut wrote:
>
> On 23/05/2023 11:14, Matteo Piva wrote:
> > Seems that it's considered an expected behavior to consider
> > optimistically the server as UP
> > when leaving MAINT mode, even if the L4 health checks are not completed yet.
To
On 23/05/2023 11:14, Matteo Piva wrote:
Seems that it's considered an expected behavior to consider
optimistically the server as UP
when leaving MAINT mode, even if the L4 health checks are not completed yet.
I consider that a quite annoying feature, but maybe I'm approaching at this in
a
> Hi Matteo,
Hi Aurelien, thanks for your reply on my issue
> > Once the activity on the underlying service has been completed and they
> > are starting up, I switch back from MAINT to READY (without waiting the
> > service to be really up).
> > The haproxy backend got immediately back in
Hi Matteo,
> Once the activity on the underlying service has been completed and they
> are starting up, I switch back from MAINT to READY (without waiting the
> service to be really up).
> The haproxy backend got immediately back in the roundrobin pool, even if
> the L4 and L7 checks are still
Hi all,
still trying to figure out the right way to to this.
Any suggestions to share with me?
Thanks,
Matteo
- Messaggio originale -
Da: "Matteo Piva"
A: "HAProxy"
Inviato: Giovedì, 11 maggio 2023 11:04:11
Oggetto: maint, drain: the right approac
Hi,
I'm trying to get into the right maintenance procedure when I have to put down
an HTTP backend for maintenance.
When I put one of the two backends in MAINT mode (disabled), the traffic is
then immediately routed only to the active backend. And this includes
persistent connections as
7 matches
Mail list logo
