 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | mod jk failover without loadbalancing | mod jk failover without loadbalancing 2003-12-09 - By Daniel Moscufo
Back
Hello All,
I have what seems to be a unique problem. I have trawled through all the
mailing lists but could not find a response.
My question is: Is it possible to setup mod_jk to do only failover
clustering without load balancing? We have an application that does much
internal caching and thus we do not want to do load balancing.
I have read through the documents and have 2 possible solutions:
1) We setup 2 worker like this:
worker.list=router
# Define a 'local_worker' worker using ajp13
worker.worker1.port=8009
worker.worker1.host=node1.domain.org
worker.worker1.type=ajp13
worker.worker1.lbfactor=100000
# Define another 'local_worker' worker using ajp13
worker.worker2.port=8009
worker.worker2.host=node2.domain.org
worker.worker2.type=ajp13
worker.worker2.lbfactor=1
# Define the LB worker
worker.router.type=lb
worker.router.balanced_workers=worker1,worker2
Notice the high lbfactor for worker 1 and low lbfactor for worker 2.
Will this do the job?
2) We setup the same configuration like this:
worker.list=router
# Define a 'local_worker' worker using ajp13
worker.worker1.port=8009
worker.worker1.host=node1.domain.org
worker.worker1.type=ajp13
worker.worker1.lbfactor=1
worker.worker1.local_worker=1
# Define another 'local_worker' worker using ajp13
worker.worker2.port=8009
worker.worker2.host=node2.domain.org
worker.worker2.type=ajp13
worker.worker2.lbfactor=1
worker.worker2.local_worker=0
# Define the LB worker
worker.router.type=lb
worker.router.balanced_workers=worker1,worker2
worker.router.local_worker_only=0
From what I gather this will mean all new requests will go to worker1
as it is set as local and worker2 isnt. If worker1 is down, as we have
set local_worker_only=0, all new requests will get forwarded to worker2.
Is this correct?
Any help would be greatly appreciated.
Daniel Moscufo
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)
|
|
|
