<div dir="ltr"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks for the info. So, to make sure I understand: haproxy will keep<br>
only 'maxconn' requests in flight to a server and sit on others until<br>
the backends catch up, right?<br>
</blockquote><div><br>True. It's really useful with ruby on rails, because mongrel can just treat one request at time.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
upstream_fair (with weight-mode=peak) will only limit the number of<br>
requests, causing Nginx to return 502 errors. It could be hacked to<br>
never return a hard error (I think), so if that's the only difference<br>
and the OP is willing to do some testing, I can implement that.</blockquote></div><br>I do not know the weight-mode option. But it's the same principle. Instead of returning an error, haproxy created a queue of requests.<br>
<br></div>