Go with v2.
Why? v2 can run with v1 configuration, and should you ever expand (for
whatever reason), then it's easy.
Dan.
On 5/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I have a two-node cluster, and need to monitor a service
continuously, if there is a network failure or service failure, then
failover to another node and reboot itself.<br />1. Which version should I
take, v1.0 or v2.0?<br />First I implemented with heartbeat 1.2.5, but it
doesn't have monitor function. Then I moved to version 2.0.8, I find it
too complex to configure. Moreover, I can't debug the problem whether the
monitor action is taken correctly, for I only can find the status section of
the cib.xml including such information.<br /><br />2. Which STONITH plugin
should I use?<br />I can't understand the saying "suicide or ssh is for
test only, not suitable for industrial usage". If I use suicide or
meatware, what's the problem?<br /><br />3. Network redundancy problem?<br
/>Now I have two NICs, two switches for redundancy, if one card fails, and
the other channel takes over. Maybe the bonding is one solution, and a link
between the switches is needed, but how can I detect the link fail between
the switches?<br /><br />Thank you for your attention and reply in
advance!<br />
hurbert
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
