2009/5/26 Schaffrath, Rene <Rene.Schaffrath@xxxxxxxxxxxxxx> > Hi, > > you need to configure fencing. If the two nodes can't see each other, they > don't know in what state the other node is and thus halt every operation. If > you configure fencing, one node will "shoot the other node in the head" > (stonithd is used in linux-ha afaik), e.g. shut it down via ilo or an ups > interface. The node only continues to operate, if the fence script notifies > success. > This is a basic principle in any cluster solutions I know and is always a > big problem in a 2-node cluster. > > Hope this makes it clearer, > René > Thanks for your answer René, The fencing was a concept that was difficult to me to underestand, but now I think its controlled. the fence devices works fine. (or I think they do). I use iLO and when I use the command fence_node nodexxx it works fine. the problem is when I unplug the cable from the service network, not the heartbeat network, ESG > > > > -----Original Message----- > > From: redhat-list-bounces@xxxxxxxxxx > > [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of ESGLinux > > Sent: Tuesday, May 26, 2009 2:03 PM > > To: General Red Hat Linux discussion list > > Subject: Re: Default params for quorumdisk > > > > Hello, > > thanks for your answer. The first link is really usefull for me. > > > > In short my problem is that when I unplug the network cable > > of the service > > interface of one of the node, the two nodes halts. I have > > looking for an > > explanation and I get this: > > > > "CMAN keeps track of cluster quorum by monitoring the count of cluster > > nodes. If more than half the nodes are active, the cluster > > has quorum. If > > half the nodes (or fewer) are active, the cluster does not > > have quorum, and > > all cluster activity is stopped." > > > > With a two nodes cluster it seams that it one fails, then the > > cluster hasn´t > > quorum and the cluster stops. > > > > So I decide to use quorum disk to see if this solve my > > problem, but I´m not > > sure if this is the problem, > > > > Greetings, > > > > ESG > > > > > > > > > > 2009/5/26 Schaffrath, Rene <Rene.Schaffrath@xxxxxxxxxxxxxx> > > > > > Hi ESG, > > > > > > I'm definitely no fan of the RHEL Cluster Suite, so I'll > > keep it short: > > > > > > must read if you use multipathing (timings): > > > http://kbase.redhat.com/faq/docs/DOC-2882 > > > > > > You probably know it already: > > > http://sources.redhat.com/cluster/wiki/HomePage > > > > > > Perhaps we can help you more if you told us what your problems are. > > > I've gone through hell searching for problems in our 2-node > > cluster and we > > > even booked a Red Hat consultant to solve our problems. But > > still there are > > > some issues which give me a headache. Make sure you have > > installed the > > > latest patches - there have been some terrible bugs in RHEL > > 5 Cluster. > > > > > > Greetings, > > > René > > > > > > > -----Original Message----- > > > > From: redhat-list-bounces@xxxxxxxxxx > > > > [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of ESGLinux > > > > Sent: Tuesday, May 26, 2009 12:38 PM > > > > To: General Red Hat Linux discussion list > > > > Subject: Default params for quorumdisk > > > > > > > > Hi all, > > > > > > > > I have my problematic 2 nodes cluster and I want to test if > > > > using quorum > > > > disk helps me with my problem. > > > > > > > > I´m using luci to setup the quorumdisk and It ask for a > > lot of params. > > > > As doc reference I use > > > > http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Cl > > > uster_Administration/s1-general-prop-conga-CA.html > > > > but there is not explanation about the default params, > > > > > > > > for example, > > > > Interval - The frequency of read/write cycles, in seconds. I > > > > have not idea > > > > what to say to that. Which is the default and how can I answer it? > > > > > > > > > > > > The same with most of the params > > > > > > > > > > > > Greetings > > > > > > > > ESG > > > > -- > > > > redhat-list mailing list > > > > unsubscribe > > mailto:redhat-list-request@xxxxxxxxxx?subject=subscribe > > > > https://www.redhat.com/mailman/listinfo/redhat-list > > > > > > > ---------------------------------------------------------------- > > > Mundipharma Vertriebsgesellschaft mbH & Co. KG > > > Mundipharma Straße 6 > > > 65549 Limburg (Lahn) > > > Tel: +49 (0)6431 701 0 > > > Amtsgericht Limburg (Lahn) HRA 624 > > > > > > Persönlich haftende Gesellschafterin: > > > Mundipharma Verwaltungsgesellschaft mbH, Sitz in Limburg (Lahn), > > > Registergericht Limburg (Lahn) HRB 462 > > > Geschäftsführer: > > > Mortimer D. Sackler M.D., Raymond R. Sackler M.D., > > > Richard S. Sackler M.D., Kathe A. Sackler M.D., > > > Jonathan D. Sackler M.D., Mortimer David A. Sackler, > > > Samantha S. Sackler-Hunt, Peter Boer, Åke Wikström, > > > Gunther Niederheide, Jürgen Feld (stellvertretend) > > > ---------------------------------------------------------------- > > > > > > > > > > > > -- > > > redhat-list mailing list > > > unsubscribe > > mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > > > https://www.redhat.com/mailman/listinfo/redhat-list > > > > > -- > > redhat-list mailing list > > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=subscribe > > https://www.redhat.com/mailman/listinfo/redhat-list > > > ---------------------------------------------------------------- > Mundipharma Vertriebsgesellschaft mbH & Co. KG > Mundipharma Straße 6 > 65549 Limburg (Lahn) > Tel: +49 (0)6431 701 0 > Amtsgericht Limburg (Lahn) HRA 624 > > Persönlich haftende Gesellschafterin: > Mundipharma Verwaltungsgesellschaft mbH, Sitz in Limburg (Lahn), > Registergericht Limburg (Lahn) HRB 462 > Geschäftsführer: > Mortimer D. Sackler M.D., Raymond R. Sackler M.D., > Richard S. Sackler M.D., Kathe A. Sackler M.D., > Jonathan D. Sackler M.D., Mortimer David A. Sackler, > Samantha S. Sackler-Hunt, Peter Boer, Åke Wikström, > Gunther Niederheide, Jürgen Feld (stellvertretend) > ---------------------------------------------------------------- > > > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjecthttps://www.redhat.com/mailman/listinfo/redhat-list
