On Oct 23, 2008, at 1:04 PM, Greg Woods wrote:
I found it was just easier to use DRBD to replicate the
database at the disk partition level, and put up with the startup time
on failover.
I wondered about that, too. Glad to hear of your experience.
Do you really have
an application where you can't even afford a few seconds down time at
failover?
No. Anything sub-60 seconds would be tolerated.
It is also unclear to me that you can bind an application to an
interface like eth0:0 that doesn't even exist when the application is
started (it is created by heartbeat at failover time). Thus it might
not
even be possible to have your apps running before failover and have
them
listening on the service address after failover. Has anyone actually
tried this?
Apache, for example, would attempt to listen on a non-existent
interface which is why I was wondering if there was a way to
dynamically bind it. This argument is probably similar to the one
above - just eat the Apache startup time on failover - and bring it
up after IP address takeover is complete.
Controlling the order so IPAddr2 fires and finishes synchronously
before starting apache or postgres, for example, is feasible,
correct? I have much more experimentation to do.
Thanks for your response,
Landon
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
