On Son 24.09.2006 23:07, snacktime wrote:
>
>I was taking a look at the source for mod_proxy_balancer this evening,
>and it looks like the simplest solution to this whole problem is to
>just add another balance method. The functions that determine what
>balance member gets the next request are pretty short. I'm a pretty
>bad C programmer, but I subscribed to the apache-dev list this evening
>and maybe I can get someone there to assist me on the finer points.
I think it would be possible to use this setup:
+------------------------+
|apache_mod_proxy_balance|
| or any other webserver |
+------------------------+
|
V
+----------------------------+
| haproxy maxconn 1 minconn 1|
+----------------------------+
| |
V V
+-------------+ +-------------+
|mongrel_rails| |mongrel_rails|
+-------------+ +-------------+
thoughts?!
Pros: haproxy balance thru all mongel_rails
check the backend if still alive
it queues the incomming requests
Cons: more complex setup
you need to manage more programms/tools
Regards
Aleks
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users
