Hi Shiby,
Shiby Maria John schrieb:
Hi,
This is my worker.properties for Apache server for clustering 3
instances of Tomcat in my machine.
# The advanced router LB worker
worker.list=router
# Define a worker using ajp13
worker.worker1.port=8009
worker.worker1.host=localhost
worker.worker1.type=ajp13
worker.worker1.lbfactor=1
# Define another worker using ajp13
worker.worker2.port=9009
worker.worker2.host=localhost
worker.worker2.type=ajp13
worker.worker2.lbfactor=10
# Define the LB worker
worker.router.type=lb
worker.router.balance_workers=worker2,worker1,worker3
worker.router.method=B
# Define another worker using ajp13
worker.worker3.port=8029
worker.worker3.host=localhost
worker.worker3.type=ajp13
worker.worker3.lbfactor=50
I expected more sessions to be hitting worker3 since it has the max
lbfactor. But the sessions are created equally in all servers.
Can some one please explain this ?
What happens, if you use the default "mthod", which is "R" = by requests?
Is your app a normal webapp (throughput focused, many relatively short
running requests)? Then "R" should be best.
Is there a reason you are talking about "sessions"? What is the
ressource you need to balance with, is it CPU (the traditional notion of
load) or more memory (because your sessions are very big)? In the latter
case, you could also use "S". Although many people use "B", I very
rarely find a use case, where "B" is a nice fit.
A nice way of following what's going on is to use a status worker:
worker.list=jkstatus
worker.jkstatus.type=status
JkMount /jkstatus jkstatus
and then point your browser to the URL /jkstatus
See: http://tomcat.apache.org/connectors-doc/reference/status.html
Regards,
Shiby
If "R" (or maybe "S") don't help you, let us know.
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
