|
On Tue, May 08, 2007 at 09:49:26AM -0400, Sal Tepedino wrote:
> On Tue, 2007-05-08 at 09:43 -0400, Sal Tepedino wrote:
> > On Tue, 2007-05-08 at 17:12 +0900, Simon Horman wrote:
> > > How are you starting the sync daemon? It sounds like however you
> > > are doing it, its only starting one. I recomend just starting
> > > both deamons up using an (ipvsadm?) init script.
> >
> > Heartbeat is starting it up (supposedly).
>
> And, actually, thinking about it, I know exactly why this is happening.
> When the machines start up, they don't have the sync process running.
> The master director starts up it's resources, which include
> "LVSSyncDaemonSwap", thus bringing up the sync process. The backup
> doesn't have any resources, so doesn't start it up. Once one failover
> happens, the backup starts it up and all is when, as once it's running,
> a loss of the resource causes heartbeat to send a signal to just cause
> the sync process to go into a backup state. Like I said. This isn't much
> of an issue, as I can put in a startup script to bring this process up.
> Just thought it might be part of the connection dropping issue.
> (retrospect says it probably isn't).
I suspect so too.
The only reason that LVSSyncDaemonSwap exists is to cope with
old (<=2.4.26) kernels that could only run the backup or master deamon,
not both. If you have a newer kernel, just run both daemons on boot.
Incidently, the sync deamon doesn't have a way to flush connections,
so I recommend setting autofailback to off.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
|
