Hi Simon,
On Tue, 2010-12-21 at 07:41 +0900, Simon Horman wrote:
> while there are a number of limitations in the synchronisation code
> I believe that what you are trying to do should work. On the backup
> do you see connections showing up in the output of ipvsadm -Lcn ?
They don't, in the prob
It's me again with a different problem.
I'm running 2.6.36.2 and keepalived 1.1.20, with two alternative
interfaces configured for ipvs sync operation, eth0.1 and eth1.3
While hunting for does-not-sync problems (other mail of yesterday +
today) I probably got confused by the master/backup partner
Hello list,
I hope you can help all users who share this same problem:
I use a 2 cluster node running on each tomat with session replication
because I need load balancing (ldirector/ipvs) and on each node the same
session information.
I configured tomcat like described here:
http://tomcat.apach
Hello Andreas.
I don't do session replication with Tomcat, I found it not to work very
well. Instead I just set anything you need sessions on to be source hash
scheduler.
Darren
-Original Message-
From: lvs-users-boun...@linuxvirtualserver.org
[mailto:lvs-users-boun...@linuxvirtualserver
Hi Darren, again ;-)
what you do is check the source IP and route it always to the same tomcat
node?
It this is true - what's about fail-over? This does not work then.
In my scenario the webapps store lots of information in memory and share it
between each nodes.
So I am freed during a b
During failover, you will lose sessions from the node that has gone
away. New connections will be sent to the remaining real server(s).
I asked the same thing 3 months ago ;)
http://lists.graemef.net/pipermail/lvs-users/2010-September/023555.html
Happy new year to you too.
Darren
-Original
