On 2012-12-06T10:49:29, Ulrich Windl <[email protected]> wrote:
> We had a network-breakdown that isolated the nodes of a 5-node cluster
> (SLES11 SP2). Interestingly each node declared itself as "DC without
> quorum" and tried to stop resources.
>
> I am surprised: Shouldn't the CRM leave resources as is while there is
> no quorum?
>
> Or is it a bug ;-)
It depends on the setting of no-quorum-policy; the default is "stop".
Normally, a node becoming isolated would be fenced next, so it tries to
stop resources before that happens. (Well, not likely that the time
window is sufficient, but it *tries*. ;-)
Seems like you want no-quorum-policy=freeze.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
