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
Hello:
Thanks for those explainations.
We will have to look further on the behavior of that server3_1 node.
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.
But if
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
Hello
Thaks. We will enable loggin to find this, but since its a production setup
will it affect performance ?
This is a set of stats. Apache was running for 3 weeks. (Hope this is clear)
mod_jk 1.2.18 with Busyness and sticky sessions (all nodes are identicical).
Name Type jvmRoute Ho
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
