On Thu, May 03, 2007 at 05:16:29PM -0400, Benjamin Lawetz wrote:
> Hi,
> 
>       I've been running some tests on my heartbeat setup with STONITH.
> When I go live, there will a serial connection, a crossover ethernet and the
> main ethernet for heartbeat. For the purpose of my tests, I've changed the
> config just to broadcast the heartbeat on the crossover cable.
>       Let's say I have node1 running resource1 and node2 running resource2
> with node2 being the DC. When I shutdown the interface:
> 
>       - Node1 notices the break, complains and doesn't do much else
>       - Node2 notices the break, complains and STONITHs Node1

Interesting. Do you have logs/config?

> I'm thinking in reality it this would be ok if Node1 freezes and stops
> responding. But what if it's Node2 that stops responding? Node1 will not
> pickup resources and the service will stop.

Shouldn't happen. You can try to kill -9 the heartbeat master
process on Node2 and see what the Node1 does.

> I know a quorum server would allow a 3rd opinion in the decision, but I feel
> this is added complexity (in 2-3 years the only failures I've had on these
> services was because of the redundancy protection. The services have been
> going strong).

Unfortunately, that is often the case.

> Is it possible to have both machines in that case try to reboot ?

Yes, I think so. But off my head I can't really say how. It also
depends on which configuration do you run: v1 or v2.

> If it fails,I'm guessing it won't be because of a link failure (3 links) and
> if it is a link failure the machine won't be able to communicate with the
> STONITH. If the machine freezes or others, I'm guessing the other node will
> be quicker to reboot it.

Right. STONITH should take care of that.

> What are your thoughts ?
> 
> -- 
> Benjamin
> TéliPhone inc.
> 
> 
> --------------
> N'envoyé pas de courriel à l'adresse qui suit, sinon vous serez
> automatiquement mis sur notre liste noire.
> [EMAIL PROTECTED]
> Do not send an email to the email above or you will automatically be
> blacklisted.
> 
> _______________________________________________
> 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

Reply via email to