On 6/24/2013 6:35 AM, nskarthik wrote: > Hi > > SPEC : Apache 2.22 > O/s :Suse ent-10 > LBS for 2 Tomcat's with Session based > > Config currently > > #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~` > <IfModule !mod_proxy.c> > LoadModule proxy_module modules/mod_proxy.so > </IfModule> > > LoadModule proxy_ajp_module modules/mod_proxy_ajp.so > LoadModule proxy_balancer_module modules/mod_proxy_balancer.so > LoadModule proxy_http_module modules/mod_proxy_http.so > LoadModule proxy_connect_module modules/mod_proxy_connect.s > > > ProxyPass /balancer-manager ! > ProxyPreserveHost On > > <Proxy balancer://mycluster> > BalancerMember http://192.168.4.32:8085/ loadfactor=50 #node1 > BalancerMember http://192.168.4.32:8086/ loadfactor=50 #node2 > ProxySet lbmethod=bytraffic timeout=15 > </Proxy> > > ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid > nofailover=On > ProxyPassReverse / balancer://mycluster/ > > #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Problem > a)If any one IP/PORT of node is down , Does the above config route to > another node which is alive one ? > b)What would happen to the session already latched to the node. ? > > I have tried evaluating both cases , but failed > > > with regards > karthik a) If one node is down, the other will be elected for new traffic. b) If there is a session sticky cookie to one node, the user will receive an error (BAD GATEWAY) because nofailover is set. This parameter ensures that if a failure occurs on the sticky node, the user stays put. -- Daniel Ruggeri --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|