Ezra Z. wrote:
On Jan 25, 2007, at 9:40 AM, Johan Sørensen wrote:
On Jan 25, 5:16 pm, Jack C. <firstname.lastname@example.org>
Is there some way to only proxy to non-busy
mongrel's? I'm running 6
mongrels, and if 1 is busy 1 out of every 6 next requests will stall.
The other 5 mongrels could easily handle them quickly. I know the
standard answer for long running tasks is a separate worker
that makes sense for really big long running tasks, but for 10-20
or so pages it seems a lot of extra work to split the logic into
multiple pieces if there is an easy way to not send more requests
Apache's mod_proxy module (and subsequently
monitoring is AFAIK limited to only being able to see if a proxy
backend is down. It cannot monitor the load or "busy-ness" of the
I know HA-Proxy and a bunch of hardware balancers does this, I don’t
think nginx, lighttpd and pound does though?
(someone should make a list somewhere with this kinda stuff ;))
So, either switch proxying software, or fix/workaround the original
Yeah Haproxy or any hardware load balancer can handle this. Apache,
lighty and nginx don’t currently. But Igor, the author of nginx told
me he will add a proxy-max-load directive so you coudl set it to 1
and that mongrel would not get another request until it returns from
the first and the requests would queue in nginx instead of in
mongrel. Probably a week or two before nginx has this built in. This
will give ngixn a significant advantage over apache and lighty.
Thanks. That sounds ideal. I will definitely keep an eye open for this
– Ezra Z.
– Lead Rails Evangelist
– Engine Y., Serious Rails Hosting
– (866) 518-YARD (9273)
You received this message because you are subscribed to the Google
Groups "Deploying Rails" group.
To post to this group,
send email to email@example.com
unsubscribe from this group, send email to
options, visit this group at