RE: mcast-interface
"Davis, Jacob" <[email protected]>
| Newsgroups | gmane.linux.highavailability.ultramonkey |
|---|---|
| Message-ID | <[email protected]> |
Very interesting! I currently have the following line in my apt/sources.list: deb http://www.ultramonkey.org/download/3/ sarge main Which gives me 1.2.3.cvs.20050404-1.0um.1 Is 1.2.3.cvs.20050927 significantly different? I did notice that I had to edit the LVSSyncDaemonSwap script in my current version in order to handle --stop-daemon= command syntax correctly. If I start both master and backup daemons on boot as you suggest, Should I remove the LVSSyncDaemonSwap line from my haresources file and create an ipvsadm rc script that looks like this:? ipvsadm --start-daemon master ipvsadm --start-daemon backup Thanks, -Jake > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Horms > Sent: Thursday, October 20, 2005 10:08 PM > To: [email protected] > Subject: Re: mcast-interface > > On Thu, Oct 20, 2005 at 01:25:58PM -0400, Davis, Jacob wrote: > > Hello, > > > > I'm setting up my first LVS HA, load balancing cluster and > my question > > is about assigning an interface for use by the ipvs_sync > daemon. I can > > see from the ipvsadm man page that you can pass the > --mcast-interface > > option on the command line but how should one handle this > when it is > > started by heartbeat? I contemplated editing the LVSSyncDaemonSwap > > resource script but thought there might be a better way. > > LVSSyncDaemonSwap::master::eth1 > > Although, these days the kernel lets you run both the master > and backup sync daemon simultaneously. So my recommendation > is to start them both using ipvsadm at boot. > > If you do want to use LVSSyncDaemonSwap, please use this version of > heartbeat: > > http://www.ultramonkey.org/download/heartbeat/1.2.3.cvs.20050927/ > > > Also, I'd like to know what the recommendation is for where > to put the > > sync traffic. Should it be on the same interface that is > used for the > > heartbeat broadcast (a private, crossover network in my > case), or is > > it better to put this traffic on the same interface that handles > > public traffic? > > There shouldn't be much traffic, and its reasonably resistant > to packet-loss, so it shouldn't really matter much where you put it. > > -- > Horms -- Ultra Monkey - http://www.ultramonkey.org/ To UNSUBSCRIBE, email to [email protected], with a body: unsubscribe ultramonkey-users [email protected] where "[email protected]" is YOUR email address.