tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Rees" <dree...@gmail.com>
Subject Re: mod_jk 1.2.17+ Recover time
Date Wed, 26 Jul 2006 02:25:32 GMT
On 7/25/06, David Rees <drees76@gmail.com> wrote:
> On 7/24/06, David Rees <drees76@gmail.com> wrote:
> > On 7/19/06, Rainer Jung <rainer.jung@kippdata.de> wrote:
> > > David Rees wrote:
> > > > Thanks that should work around my issue quite nicely. I'll check out
> > > > SVN and give a whirl (unless a new tag is to be rolled again shortly?)
> > >
> > > Try 1.2.18.
> >
> > 1.2.18 works much better, thanks!
>
> I spoke too soon. I've been testing 1.2.18 further, and recover time
> while appearing to change, I can not get mod_jk to actually recover
> any faster than 60 seconds, even when recover time is set to 1.

OK, It seems that the docs could use some clarification (can't be good
if the devs seem to be a bit confused as well as to what they do), but
you also need to set worker.maintain to a low value as well. mod_jk
acts like it uses the minimum of either worker.maintain or the
lb_worker's recover_time to determine the minimum amount of time a
worker should be down.

By setting worker.maintain to 10 and lb_worker's recover_time to 10 I
can get a reasonable recovery time for a worker.

-Dave

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


Mime
View raw message