|
We are having a problem with our LVS balanced Tomcat cluster. It works
fine for most people but we've been having problems with people coming
from certain ISP's through proxies. We have sticky load balancing and
do NOT have session replication (old app).
Apparently, they are routing through different proxy servers depending
upon whether the protocol is http or https. The result is that they
come at us from two different IP addresses depending upon whether their
connection is http or https, and LVS can't tell that they are the same
session, so it often routes them to different servers. When they get
bounced to another server, their session data is not there, and everything
breaks.
Is there a way for LVS to see Tomcat session id's and use that for
stickyness? I'm guessing not, but I figured it's worth asking anyway.
Implementing session replication is going to be painful, because the app
is huge, and has been around a long time, and wasn't designed with that
in mind.
Even if we retrofit session replication, from what I understand, it
seriously
impacts performance when users get bounced from one server to another.
Is it too much to ask that ISP's route ports 80 and 443 from the same user
through the same proxy server?
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
