Hello Arthur, On Wed, Jun 3, 2020 at 11:38 AM Artur <hapr...@netdirect.fr> wrote: > What is the risk to trigger this bug in real life ? How to avoid it > before the next haproxy release ? > In my setup haproxy 2.1.5 has threads enabled by default (Debian Buster > backports).
You will trigger this issue if you are in the following cumulative cases: - using a non-default `pool-purge-delay` value, the higher the value is, the easiest it is to reproduce - changing the servers state at run time (i.e from running to maintenance state) and/or change ip/port of servers at runtime for a given backend. So basically, it will impact heavy users of the runtime API. Best, -- William
