tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jess Holle <je...@ptc.com>
Subject Re: mod_proxy_balancer issue
Date Wed, 27 Aug 2008 14:37:48 GMT
Mladen Turk wrote:
> Jess Holle wrote:
>>
>> I'm quite willing to help, but you're clearly much more familiar with 
>> both mod_jk and APR/MPM than I am, so I suspect I'd just get in the 
>> way except at the testing level.
> Well, I plan to create mpm watchdog hook system first.
> I'll also create a small callback in mod_proxy, just
> to maintain the connection pool so you are free to implement
> any additional mod_proxy interval operations (like heath checking)
> from there.
Is there already something along these lines in mod_jk (or more 
specifically the IIS connector)?

I did a little simplistic testing and haven't gotten down and dirty to 
debug this, but I have no managed to figure out any configuration of 
mod_jk where the load balancers' "dead" workers will be tested in the 
background and avoid testing this with foreground requests.  I have a 
simple "ping" request that takes many seconds all too often, presumably 
delayed by re-checking all the dead workers.

I have a worker.maintain of 15 and a recover_time for my balanced worker 
of 30 -- under the theory that background maintenance should be able to 
test any "dead" connections and mark them as recently tested without any 
request threads ever checking the workers.  This assumes that the 
recover_time is only observed by request threads, though.

Is there a means of achieving background-only (or nearly so) testing of 
dead workers with mod_jk?  That's what I'm looking for in both jk and 
mod_proxy_ajp connectors.  I guess I was hoping/assuming it was there in 
mod_jk from reading the docs.

--
Jess Holle


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message