Hi Andrew, Can I use heartbeat-2.1.3 with Pacemaker 1.0? Or do I need to upgrade to higher version of heartbeat for cluster communication? >From the "Versions and Compatibility" section of >http://www.clusterlabs.org/wiki/Install I can see that heartbeat 3 is tested >with Pacemaker 1.0. So I think I should upgrade to heartbeat 3.
Do you suggest using OpenAIS instead of heartbeat for cluster communication? Does Pacemaker mandatorily need cluster file system like GFS? We also have another clustering alternative s/w Red Hat Cluster Suite (RHCS). What is your opinion about it? RHCS gives me impression that it is a commercial version of LinuxHA. Does LinuxHA and RHCS has any relation? Thanks in advance for your guidance. Regards, Prasad. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Beekhof Sent: Wednesday, December 02, 2009 4:19 PM To: General Linux-HA mailing list Subject: Re: [Linux-HA] Issue with stopping resources On Wed, Dec 2, 2009 at 11:30 AM, Kukkala Prasad <[email protected]> wrote: > Hi Andrew, > > Thanks for your response. > > I should be able to configure MySQL HA with SAN. Which version of LinuxHA do > you suggest and where can I download the rpm of the same? Pacemaker 1.0 - http://www.clusterlabs.org/wiki/Install > > Regards, > Prasad. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Andrew Beekhof > Sent: Wednesday, December 02, 2009 3:43 PM > To: General Linux-HA mailing list > Subject: Re: [Linux-HA] Issue with stopping resources > > On Tue, Dec 1, 2009 at 5:46 PM, Kukkala Prasad <[email protected]> wrote: >> Hi All, >> >> I have configured ha cluster with two nodes and two resources IP address and >> httpd service. I am working with heartbeat-2.1.3-3.el5.centos CentOS 5.3. > > Far too old. > >> I followed the >> http://www.novell.com/documentation/sles10/heartbeat/?page=/documentation/sles10/heartbeat/data/heartbeat.html >> documentation. >> >> I want to discuss about 2 issues and 2 questions > >> Issue1: >> I want to stop resources on a node if the network connection is not >> available (default gateway is not reachable). >> When I stop network of node 1 (using "service network stop" command) >> resources are automatically launching on node2 but on node1 resources are >> still running. Please check the below configuration and kindly advice me >> what is missing? Sorry for the big xml but I have to share full >> configuration to check the missing stuff. > > http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/ch09s03s03.html > >> Issue2: >> Once the network is up resources running on node2 are moving to node1. In my >> ha.cf file I have set auto_fallback false. But still resources are coming >> back to node1. I don't want this. How to avoid this? > > Look up resource-stickiness. > >> >> Question1 >> I want to implement a logic (quorum I suppose) which should enable me decide >> whether to run resources on given node or not. This is required for me to >> avoid accessing SAN simultaneously by two nodes. How to do this? > > quorum and fencing are already supported. > the problem with quorum in 2-node heartbeat clusters is that it always > pretends that it has it. > >> >> Question2 >> Is there any reference configuration (cib.xml) available for >> HeartBeat+SAN+MySQL active-passive configuration. > > You could try reading the cluster form scratch document at > http://clusterlabs.org/wiki/Documentation and substitute mysql for > apache. > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > > The information contained in this communication is confidential, intended > solely for the use of the individual or entity to whom it is addressed and > may be legally privileged and protected by professional secrecy. Access to > this message by anyone else is unauthorized. If you are not the intended > recipient, any disclosure, copying, or distribution of the message, or any > action or omission taken by you in reliance on it is prohibited and may be > unlawful. Please immediately contact the sender if you have received this > message in error. This email does not constitute any commitment from Cordys > Holding BV or any of its subsidiaries except when expressly agreed in a > written agreement between the intended recipient and Cordys Holding BV or its > subsidiaries. Cordys is neither liable for the proper and complete > transmission of the information contained in this communication nor for any > delay in its receipt. Cordys does not guarantee that the integrity of this > communication has been ma > intained nor that the communication is free of viruses, interceptions or > interference. If you are not the intended recipient of this communication > please return the communication to the sender and delete and destroy all > copies. > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
