Hello Mladen,
hmm, with your example I got a Internal Server Error after I disable or drop active node2 and start a new session request! :-(
All request with active node2 session work properly when node2 shutdown! What I want is that after a failure,
the node1 got all requests. This szenario work very well with old local_worker mode.
Here my test confguration:
worker.list=lb,status
worker.node1.port=9012 worker.node1.host=localhost worker.node1.type=ajp13 worker.node1.disabled=true
worker.node2.port=9022 worker.node2.host=localhost worker.node2.type=ajp13 worker.node2.disabled=false worker.node2.redirect=node1
worker.lb.balance_workers=node1,node2 worker.lb.type=lb
worker.status.type=status
Peter
Mladen Turk schrieb:
Peter Rossbach wrote:
Hello Mladen,
after a very long thinking I have missing a hot Standby feature, when we remove local_work flag.
How I can configure this without local_work flag? I thing we can rename the flag to preferred_worker.
OK. Worker B used as hot standby:
worker.A.redirect=B worker.B.disabled=True
worker.LB.sticky_session=True worker.LB.balance_workers=A,B
If you wish to have a hot-standby tomcat cluster group, then use domains. For single workers use worker names.
So worker B is initially disabled. Worker A has redirect of 'failover' to B. Worker B will not receive any requests unless worker A gets in error state or disabled. If worker A gets disabled existing sessions will be still served, new one will go to B.
Later you can use jkstatus, and switch their roles.
Mladen.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
