*** (0.28) *** Re: [Linux-HA] quorum server not available

[Alan Robertson]

Andreas Kurz wrote:
> On 2/26/07, Lars Marowsky-Bree <lmb at suse.de> wrote:
>> On 2007-02-26T16:05:06, Andreas Kurz <andreas.kurz at gmail.com> wrote:
>>
>> > Yes, that's the point why I was thinking of using the quorumd ... to
>> > get a "real" quorum. In case there is a complete network split I want
>> > the resources to halt on both nodes
>>
>> It _is_ a real quorum for the specific case. The resources _will_ halt
>> and/or not be brought online because no fencing is possible.
>>
>> > and not two DCs.
>>
>> This is a conceptual point I'd like to correct. You _will_ have two DCs,
>> because there's always one DC per cluster partition; it just so happens
>> that this then will decide to not do anything ;-)
> 
> But only if you configured fencing ;-)

Fencing and quorum are related concepts, but with some distinctions.

You can configure the no_quorum_policy to be stop, ignore, or freeze.
_no_quorum_policy_ is what determines what happens when we lose quorum.

  stop:   Stop all resources
  ignore: pretend we have quorum and go on like nothing happened
  freeze: Continue to run the resources we have, but don't start
          any we think the now-dead side was running.

And, you can separately and independently configure
	stonith_enabled
	stonith_action
and	startup_fencing

In order to keep both sides from shooting each other, we require quorum
before we STONITH anyone.

-- 
    Alan Robertson <alanr at unix.sh>

"Openness is the foundation and preservative of friendship...  Let me
claim from you at all times your undisguised opinions." - William
Wilberforce