On 05/11/2018 15:05, Jim Jagielski wrote: > I was thinking about something more robust and usable than heartbeat (due to > multicast) but similar in basic concept.
I remember trying mod_heartmonitor with a simple listener like <Listener className="org.apache.catalina.ha.backend.HeartbeatListener" Port="8009" ProxyList="127.0.0.1:7779" /> Where ProxyList is the lit of httpd that are able to proxy to tomcat back-ends. See http://jfclere.blogspot.com/2009/04/ I guess I need to revisit that to use mod_prxy_balancer logic. > >> On Nov 5, 2018, at 8:48 AM, jean-frederic clere <[email protected]> wrote: >> >> On 30/10/2018 13:53, Jim Jagielski wrote: >>> As some of you know, one of my passions and area of focus is >>> on the use of Apache httpd as a reverse proxy and, as such, load >>> balancing, failover, etc are of vital interest to me. >>> >>> One topic which I have mulling over, off and on, has been the >>> idea of some sort of universal load number, that could be used >>> and agreed upon by web servers. Right now, the reverse proxy >>> "guesses" the load on the backend servers which is OK, and >>> works well enough, but it would be great if it actually "knew" >>> the current loads on those servers. I already have code that >>> shares basic architectural info, such as number of CPUs, available >>> memory, loadavg, etc which can help, of course, but again, all >>> this info can be used to *infer* the current status of those backend >>> servers; it doesn't really provide what the current load actually >>> *is*. >>> >>> So I was thinking maybe some sort of small, simple and "fast" >>> benchmark which could be run by the backends as part of their >>> "status" update to the front-end reverse proxy server... something >>> that shows general capability at that point in time, like Hanoi or >>> something similar. Or maybe some hash function. Some simple code >>> that could be used to create that "universal" load number. >>> >>> Thoughts? Ideas? Comments? Suggestions? :) >> >> having the back-ends to provide the load they are able to handle >> lbfactor (via w_lf or somethere similar. That requires the back-ends to >> be able to send request to httpd balancer-manager handler. >> >>> >> >> >> -- >> Cheers >> >> Jean-Frederic > > -- Cheers Jean-Frederic
