On Tue, Mar 30, 2021 at 10:17:01AM +0200, Lukas Tribus wrote: > Hello Thomas, > > > this is a known issue in any release train other than 2.3 ... > > https://github.com/haproxy/haproxy/issues/1196 > > However neither 2.3.7 (does not contain the offending commits), nor > 2.3.8 (contains all the fixes) should be affected by this. > > > Are you absolutely positive that you are running 2.3.8 and not > something like 2.2 or 2.0 ? Can you provide the full output of haproxy > -vv?
I must say that I'm completely puzzled because that's exactly the issue that affected 2.3.7, and which was fixed in 2.3.8. Here it seems to do exactly the opposite! And I've tested using the same method (http_req_rate(2s) and 500ms this time to cover both >1s and <1s). So I don't know what to say. I'm now extremely tempted to revert all these fixes because in the end the original problem was much less visible for most users :-( I'm now trying with this *exact* config in case I missed something else. Thanks, Willy
