On Thu, Aug 6, 2009 at 3:41 PM, Robinson, Eric <[email protected]>wrote:
> [Sebastien] > > Are you using the same syncid in a different cluster on > > the same network? > > Hi Sebastien, thanks for your reply. I understand the problem you are > referring to, but unfortunately that's not the problem in our case. We > only have one LVS cluster. > > I don't fully understand why you needed to put LVSSyncDaemonSwap in > haresources.cf. If you start the master abd backup daemons on both > cluster nodes, and make sure the syncids do not conflict, then why would > any swapping be necessary? > > I wonder if this is the root of my problem. Maybe the master gets new > connections and sends them to the backup, then the backup sends them > back to the master as new connections, and somewhere in the mix the > timeouts are getting messed up. Eric, About the timeout issue on the backup (ie the point number 3 of your first email). When the master sends a new connection information to the backup, the timeout of this connection on the backup is by default 3min. If the connection is idle for more than 3 minutes it will disappear from the backup while it might still be registered on the master. There is a good explanation of this here : http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.server_state_sync_demon.html Regards Sebastien _______________________________________________ Please read the documentation before posting - it's available at: http://www.linuxvirtualserver.org/ LinuxVirtualServer.org mailing list - [email protected] Send requests to [email protected] or go to http://lists.graemef.net/mailman/listinfo/lvs-users
