Thanks. I got it after read 'man qdisk'. The tiebreaker ip is described here. ext jumanjiman@xxxxxxxxx wrote: > Look up "quorum disk". You can add a heuristic based on ping or just about any other shell command. The heuristic acts like a ghost node toward quorum. > An actual disk is not needed. > > -paul > > Sent via BlackBerry by AT&T > > -----Original Message----- > From: Mockey Chen <mockey.chen@xxxxxxx> > > Date: Mon, 09 Feb 2009 09:52:06 > To: linux clustering<linux-cluster@xxxxxxxxxx> > Subject: Re: How to avoid two-nodes cluster > split-brain withoutshared storage > > > Hi Barry Brimer, > > Thanks your suggestion. > 'tiebreaker ip', I searched the cluster documents, and only find the > definition of 'tiebreaker ip', but there is no description on how to > configure it. > Could you give some more detail about how to configure it. > > > > ext Barry Brimer wrote: > >> I believe you want to use the tiebreaker ip .. which should be set to >> the default gateway. Presumably the machine that is malfunctioning >> would be unable to reach the gateway, while the one that is >> functioning correctly could. >> >> On Sat, 7 Feb 2009, Jeff Sturm wrote: >> >> >>> We faced the same question, and decided that for reliability, it was >>> best to add an inexpensive third node to a cluster. >>> >>> The third node need not run any cluster services (rgmanager, GFS, CLVM >>> etc.) other than fencing. This is a far lower cost than adding shared >>> storage simply for a quorum disk. >>> >>> >>>> -----Original Message----- >>>> From: linux-cluster-bounces@xxxxxxxxxx >>>> [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Mockey Chen >>>> Sent: Friday, February 06, 2009 3:18 AM >>>> To: linux clustering >>>> Subject: How to avoid two-nodes cluster >>>> split-brain withoutshared storage >>>> >>>> Hi, >>>> >>>> I have a two node cluster, due to design limitation, there is >>>> no shared storage exist. So I can not use quorum disk. >>>> >>>> Is there any other reliable way to prevent split-brain? >>>> I searched google, but I can not found any solution suitable >>>> for my situation. >>>> >>>> Any comment is appreciated. >>>> >>>> >>>> Best Regards. >>>> Chen Ming >>>> >>>> -- >>>> Linux-cluster mailing list >>>> Linux-cluster@xxxxxxxxxx >>>> https://www.redhat.com/mailman/listinfo/linux-cluster >>>> >>>> >>>> >>> -- >>> Linux-cluster mailing list >>> Linux-cluster@xxxxxxxxxx >>> https://www.redhat.com/mailman/listinfo/linux-cluster >>> >>> !DSPAM:498dddd510851773614401! >>> >>> >>> >> -- >> Linux-cluster mailing list >> Linux-cluster@xxxxxxxxxx >> https://www.redhat.com/mailman/listinfo/linux-cluster >> >> > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster > > -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster