I just tested with mod_jk 1.2.19 and it still seems as though the distance
parameter is being ignored. Output from the status/monitor.page shows
mod_jk alternating between tomcats with different distance values in
workers.properties.
How can I troubleshoot this further?
Here's my workers.properties...
[EMAIL PROTECTED]:/usr/local/etc/apache$ cat workers.properties
workers.tomcat_home=/usr/local/tomcat5.5
workers.java_home=/usr/local/jdk
ps=/
worker.list=tomcat
worker.tomcat.type=lb
worker.tomcat.socket_timeout=195
worker.tomcat.balance_workers=localhost,ritin
worker.tomcat.sticky_session=False
worker.localhost.port=8009
worker.localhost.socket_timeout=195
worker.localhost.host=localhost
worker.localhost.type=ajp13
workers.localhost.distance=10
worker.localhost.lbfactor=1
worker.ritin.port=8009
worker.ritin.host=ritin
worker.ritin.type=ajp13
workers.localhost.distance=20
worker.ritin.lbfactor=1
And some version information...
[EMAIL PROTECTED]:~$ grep mod_jk /var/log/apache/error_log |tail -1
[Thu Dec 7 16:13:04 2006] [notice] Apache/1.3.37 (Unix) mod_perl/1.29
mod_ssl/2.8.28 OpenSSL/0.9.7e-p1 mod_jk/1.2.19 configured -- resuming normal
operations
Dane
Rainer Jung-3 wrote:
>
> The new attribute distance will help you. It was first implemented for
> version 1.2.16, which is in the process of being released (see my other
> answer).
>
> Please test and let us know your results.
>
> thuss2 schrieb:
>> We have 10 web servers with Tomcat's running on them and a mod_jk
>> configuration to prefer the tomcat on localhost and only failover to
>> another
>> machine if the local one fails. This worked fine under our older mod_jk,
>> however, we just upgraded to 1.2.15 and now it that the local_worker
>> properties are no longer supported, it's load balancing every request.
>>
>> So I checked out the workers.properties options page:
>> http://tomcat.apache.org/connectors-doc/config/workers.html and noticed
>> the
>> new distance option so that I can give localhost a distance of 0 and
>> everything else a greater distance so that the load balancer should
>> always
>> prefer localhost. However, it seems to be ignoring the distance property
>> completely and load balancing every request. Can anyone suggest what I
>> might
>> try to get it to always use the local tomcat for requests unless it
>> fails:
>>
>> worker.list=tomcat
>> worker.tomcat.type=lb
>> worker.tomcat.socket_timeout=195
>> worker.tomcat.balance_workers=localhost,latin1,latin2,...
>> worker.tomcat.sticky_session=False
>>
>> worker.localhost.port=8009
>> worker.localhost.host=localhost
>> worker.localhost.type=ajp13
>> worker.localhost.lbfactor=1
>> worker.localhost.distance=0
>>
>> worker.latin1.port=8009
>> worker.latin1.host=latin1
>> worker.latin1.type=ajp13
>> worker.latin1.lbfactor=1
>> worker.latin1.distance=1
>>
>> worker.latin2.port=8009
>> worker.latin2.host=latin2
>> worker.latin2.type=ajp13
>> worker.latin2.lbfactor=1
>> worker.latin2.distance=1
>>
>> Thanks,
>> Todd
>>
>> --
>> View this message in context:
>> http://www.nabble.com/mod_jk-failover-and-preferring-localhost-t1825380.html#a4979143
>> Sent from the Tomcat - User forum at Nabble.com.
>>
>>
>> -
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/mod_jk-failover-and-preferring-localhost-tf1825380.html#a7750978
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
