Re: Redhat without qdisk

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Aderson

Talking about the delay parameter, I think the people work in the redhat support doesn't the man pages

Because i hate the work around of using delay in the fencing session

I found some times ago
========================================================
 master_wins="0"
            If set to 1 (on), only the qdiskd master will advertise its votes to CMAN.  In  a  network  partition,  only  the
            qdisk master will provide votes to CMAN.  Consequently, that node will automatically "win" in a fence race.
========================================================

And i can tell you work well, just the master fence the passive node

I would to know

what are the necessary requirements to work in redhat?

Because i received some many stupid answers for the support

One example

The fisrt time i found a fencing Race
===================================================
The Redhat answer was

I see you use a cluster private network and public, you can use a
heuristics for monitor both networks
Other Redhat Limitation, the ip.sh doesn't monitor the connectivity with gateway just the Link

====================================================

I don't whay Redhat doesn't change this type of cluster

I prefer corosync+pacemaker

Il giorno 12 aprile 2012 17:12, Anderson, John(Patni) <John.Anderson4@xxxxxxxxxxxxxxxx> ha scritto:

I don’t normally chime in, but running RHEL on a two node cluster we have found that the only way to ensure fencing works properly is with a 2gb qdisk.  The option you were told works correctly less than 50% of the time as both attempt to fence the other.  We set up a delay on the passive node so if the active node gets in trouble the qdisk switches to the passive at the end of the delay, and the fencing takes place.  The process takes about 5 minutes or so.

 

John A.

 

From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Daniel Bourque
Sent: Thursday, April 12, 2012 7:47 AM
To: linux clustering
Subject: Re: Redhat without qdisk

 

A qdisk is just another way to maintain quorum in cluster. there is a special two node cluster mode designed to allow for quorum to be maintained by the surviving node.

 

<cman two_node="1" expected_votes="1">

</cman>

 

But it's not very clear to me what happens with fencing if both nodes get partitioned on the network. Do they both try to fence each other off ?

 

 

-- 
Dan

 


From: linux-cluster-bounces@xxxxxxxxxx [linux-cluster-bounces@xxxxxxxxxx] on behalf of emmanuel segura [emi2fast@xxxxxxxxx]
Sent: Thursday, April 12, 2012 9:25 AM
To: linux clustering
Subject: Redhat without qdisk

Hello all List

I have a big question about qdisk in a two cluster

one of out clients has too many cluster in two nodes configuration and one RedHat technical came to us and said that there is no need to use the qdisk

I would to know if this is true

I really think it's a bad idea

--
esta es mi vida e me la vivo hasta que dios quiera


--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster



--
esta es mi vida e me la vivo hasta que dios quiera
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux