Hello,
Am 02.08.2017 um 14:41 schrieb Claudio Kuenzler: > Quick update: I set a really short timeout on the queue (timeout queue 100) > so HAProxy returns a 503 to the 7th connection almost immediately as well. > That's what I was about to propose, yes. You should even be able to set "timeout queue" to 0 (which doesn't work for the maxqueue parameter). At the very least though setting it to 1 will lead to just 1 ms of delay in responding with the 503 message. > However I doubt that this is a proper solution. Any other ideas? The proper solution depends on the problem you are trying to solve. What is the problem you are trying to solve? > Is there a way to disable queuing at all for a backend? I don't think so, and I can't think of a reason why you would wanna do that. Can you elaborate the use-case here? What would happen if the client waits in the queue for 5 - 10 ms in the queue? > PS: Yes, "no option redispatch" has been set on this backend. Purposely to > not redispatch to another backend server if an existing session (cookie) is > detected. "no option redispatch" is already the default. You probably want "option persist" [1] instead? Regards, Lukas [1] https://cbonte.github.io/haproxy-dconv/1.7/configuration.html#4.2-option%20persist
