> In fact at some point I had a backend with 5 srv from config + 3 > dynamically inserted. Those new ones got about 50 requests pushed to > them, until they reaches the slowstart delay(I think, must investigate > more), when they stopped being selected for new connection. The status > was L7OK for the 8 srv regardless of the way they arrived. You're right, I made the same observation during the tests but I forgot to mention it: A server that is in STARTING phase is immune to this issue: it only occurs when server state is RUNNING (either when no slowstart delay is specified, or at the end of the slowstart period if specified)
Also, last observation: if you remove the maxconn on a "buggy" server (that previously had the maxconn set using the cli): echo "set maxconn server farm/t1 0" | nc -U /tmp/ha.sock The issue is gone: you can set the maxconn back to a positive value without problems. I'll keep investigating by looking at the code :)
