> 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 the roundrobin pool, even if 
> > the L4 and L7 checks are still validating that the underlying service is 
> > still DOWN (service is still starting, could take time). 

> I would wait for others to confirm or infirm, but meanwhile the 
> situation you described makes me think of an issue that was revived on 
> Github a few weeks ago: https://github.com/haproxy/haproxy/issues/51 
> (server assumed UP when leaving MAINT before the checks are performed) 


yes, I saw that issue on Github, but I can also see the lukastribus 's comment 
on that: 

  When health checks are used, but did not start yet or the status is not yet 
determined, 
  then the current server status will be UP. This is documented and expected 
behavior. 


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

Waiting for others to comment such issue to better understand.


Thanks, 
Matteo 

Reply via email to