[Linux-cluster] question about 2 nodes cluster

[ESGLinux]

Thank you Ian,
I´l take your answer in account,

Greetings,

ESG

2009/6/8 Ian Hayes <cthulhucalling at gmail.com>

> You don't need a third node or quorum disk... A 2-node cluster is sort of a
> special case, which is why there is a special config line for a setup with
> only 2 nodes. I'm running a couple of 2-node clusters right now with no
> quorum disk. The main issue I've encountered is that they can go split-brain
> easily, and you get to watch both nodes fence each other off endlessly.
> Adding clean_start="1" to the fence_daemon line helps prevent this, but a
> quorum disk would be better if you're absolutely committed to a 2-node
> setup.
>
> I'm running a test cluster at this moment with 3 nodes and a 1Gb quorum
> partition that is shared out via iSCSI. I sort of discovered that I needed a
> quorum disk the hard way after taking 2 nodes down and the suriviving node
> gave up due to the cluster being inquorate.
>
>
> On Mon, Jun 8, 2009 at 5:22 AM, ESGLinux <esggrupos at gmail.com> wrote:
>
>> Hi all,
>> I have one  existential question about two nodes cluster. I have read that
>> for 2 nodes cluster is necessary a third element to give stabilty to the
>> cluster.
>>
>> One way is to add a third node, so its not a 2 nodes cluster. For me its
>> not an answer because It becomes another kind of cluster ( 3 nodes cluster)
>>
>> Other, is to use qdisk (this is the way I´m trying nowadays)
>>
>> My question is if it´s absollutely necesary this third element in the
>> architecture. and If so which are the options, ?
>>
>> thanks in advance
>>
>> ESG
>>
>>
>> --
>> Linux-cluster mailing list
>> Linux-cluster at redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-cluster
>>
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20090608/0b3fa3a2/attachment.htm>