We're running a mod_proxy_balancer in front of our webmail-servers,
and use cookies to keep sessions sticky:
<Proxy balancer://atmailcluster>
BalancerMember http://atmail1.mydomain.com:80 route=atmail1
loadfactor=100
BalancerMember http://atmail2.mydomain.com:80 route=atmail2
loadfactor=100
BalancerMember http://atmail3.mydomain.com:80 route=atmail3
loadfactor=100
BalancerMember http://atmail4.mydomain.com:80 route=atmail4
loadfactor=100
BalancerMember http://atmail5.mydomain.com:80 route=atmail5
loadfactor=100
</Proxy>
and each of the real-servers sets a cookie on every access:
RewriteRule .* - [CO=balancercookie:balancer.atmail1:.mydomain.com:70]
But, how can I get a node out of production without disturbing the users?
I.e. how do I stop distributing new sessions to f.ex. "atmail1", and only
route existing connections to it until all cookies are expired ?
Setting "loadfactor=1" does not help, since it still will be getting a tiny
bit of new load, and then set the cookie again.
Setting "redirect=atmail2":
BalancerMember http://atmail1.mydomain.com:80 route=atmail1
loadfactor=1 redirect=atmail2
also seems to be letting trough some new load to atmail1.
Any ideas ?
-jf
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
