Mohan2005 wrote:
On the 'P' option which was recommended by Mladen Turk some time ago when we
had issues (share memory locking) with a older version of mod_jk ( <1.2.15),
we have left it as it is.
There definitely were issues concerning optimistic locking around
1.2.15, but we expect them to b
t is.
But if you recommend that 'O' locking gives better performance on new mod_jk
versions we will be looking into changing it after testing under our
applications.
Thanks
--
View this message in context:
http://www.nabble.com/Mod_jk-load-balacing-algorithm-tf2064844.html#a57018
Hi,
Mohan2005 schrieb:
> Hello
>
> Thaks. We will enable loggin to find this, but since its a production setup
> will it affect performance ?
The numbers suggest, that you've got
210.000 * 12(instances) / 21 (days) = 120.000 requests/day
So depending on the time distribution, this should boild
, server4_2, server1_3, server2_3,
server3_3, server4_3
worker.loadbalancer.lock=P
worker.loadbalancer.method=B
worker.loadbalancer.local_worker_only=1
--
View this message in context:
http://www.nabble.com/Mod_jk-load-balacing-algorithm-tf2064844.html#a5700083
Sent from the Tomcat - User forum
Hi,
Mohan Wickramasinghe schrieb:
> Hello
>
> We are using the "new" Busyness method with 1.2.18
> We have also using 'sticky sessions'.
>
> Clarification on
> "> As soon as there will be real load, behaviour will differ."
>
> We have 9 nodes on 3 identitical servers with identical settings, lb
Hello
We are using the "new" Busyness method with 1.2.18
We have also using 'sticky sessions'.
Clarification on
"> As soon as there will be real load, behaviour will differ."
We have 9 nodes on 3 identitical servers with identical settings, lb
factor equal on all nodes, but we see one node which
Subject: Re: Mod_jk load balacing algorithm
mod_jk neither supports round-robin, nor random load-balancing.
Currently you can choose between three algorithms:
method=B (busyness): choose the worker with the lowwest number of
requests currently in processing.
method=R (requests): choose the worker
mod_jk neither supports round-robin, nor random load-balancing.
Currently you can choose between three algorithms:
method=B (busyness): choose the worker with the lowwest number of
requests currently in processing.
method=R (requests): choose the worker that did the lowest number of
requests
Is it possible to change mod_jk's load-balacing algorithm to random (from
round robin)?
If yes, how?
TIA
Sidd
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comma
