Welcome! Log In Create A New Profile


Randomness in hard-stop-after

Posted by Samuel Reed 
Samuel Reed
Randomness in hard-stop-after
February 08, 2018 08:00PM
When reconfiguring across a large web tier, it's possible that many
HAProxy reloads are initiated at nearly the same time. We have a large
number of long-lived TCP sessions, so we must use hard-stop-after to
eventually kill them off, or HAProxy instances will remain open for days.

It would be very helpful to have an option like
`spread-hard-stop-after`, similar to `spread-checks`, to introduce some
random variance into the timeout such that the disconnection of these
sessions does not cause a major traffic event across the stack.

Also, thank you very much for the 1.8.4 release!
Sorry, only registered users may post in this forum.

Click here to login