Re: maint, drain: the right approach

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 th

Re: maint, drain: the right approach

> 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

Re: maint, drain: the right approach

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 approach

maint, drain: the right approach

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 well

monitor-uri: right way to approach a maintenance in cascaded haproxys

Hi all, I'm trying to set up our haproxys according to the following cascaded schema: HTTP CLIENT: --> HAPROXY1 HTTP Frontend --> HAPROXY 1 Backend (/health monitoring, RR to Haproxy2's frontends and Haproxy3's frontends) --> HAPROXY2 HTTP Frontend (exposing /health monitor-uri) --> HAPROXY2