The guts are all there for this to work on the proxy side. We just need to make a module out of it. The question of header name and what-not can be solved by making it configurable. The real $1,000,000 question is what your backend is and how you can gather load information. This would be trivial to do with a Servlet filter in a J2EE app, but I am not sure about other implementations (my own ignorance rather than it being technically impossible). -- Daniel Ruggeri
-------- Original Message -------- From: Jim Jagielski <j...@jagunet.com> Sent: November 20, 2014 7:36:11 AM CST To: users@httpd.apache.org Subject: Re: [users@httpd] Load balancing with load detection on backend servers ? The only real question is how the load value of the backend systems can be known and then "told" to Apache. I had proposed awhile ago using some sort of custom HTTP X-header to send that info. > On Nov 19, 2014, at 3:28 AM, ulrich.her...@t-systems.com wrote: > > Hi all, > > I know the load_balancing-policies bybusyness, byrequests, bytraffic and > heartbeat. > > We have a frontend apache, that acts as forwarding proxy to 8 backend servers. > BUT: We want do route the next request to that backend server with least load. > > Is there any apache module, that can do this ? > (We use linux and apache 2.4) > > Heartbeat is not usable, because our backends do not run apache, but > something else. > > Uli --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
