Well.. If you are using an active/standby scenario, without a shared storage, probably you can make use of CARP/UCARP <a href="http://en.wikipedia.org/wiki/Common_Address_Redundancy_Protocol">http://en.wikipedia.org/wiki/Common_Address_Redundancy_Protocol</a> <a href="http://www.ucarp.org/project/ucarp">http://www.ucarp.org/project/ucarp</a> -- Flávio do Carmo Júnior aka waKKu <div class="gmail_quote">On Thu, Oct 23, 2008 at 2:01 PM, Lon Hohberger <<a href="mailto:lhh@redhat.com">lhh@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Thu, 2008-10-16 at 17:10 +0800, Chen, Mockey (NSN - CN/Cheng Du) wrote: > Hi, > > I want to set up a two node cluster, I use active/standby mode to run > my service. I need even one node's hardware failure such as power cut, > another node still can handover from failure node and the provide the > service. > > In my environment, I have no shared storage, so I can not use quorum > disk. Is there any other way to implement it? I searched and found > 'tiebreaker IP' may feed my request, but I can not found any hints on > how to configure it ? Since you have no shared data, you may be able to run without fencing. That should be pretty straightforward, but you might need to comment out the "fenced" startup from the cman init script. In this case, the worst that will happen is both nodes will end up running the service at the same time in the event of a network partition. The other down side is that if the cluster divides into two partitions and later merges back into one partition, I don't think certain things will work right; you will need to detect this event and reboot one of the nodes. -- Lon -- Linux-cluster mailing list <a href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/linux-cluster" target="_blank">https://www.redhat.com/mailman/listinfo/linux-cluster</a> </blockquote></div>