No probs. I've had to bring myself up to speed pretty quickly with all this. I'm finding the current incarnation (pacemaker 1.0.3, openais 0.80.3 shipped with SLES 11 HAE) to be excellent and compared to the old heartbeat 2.1.3 stuff I used to dabble with it's a lot nicer. The crm shell is awesome.
At the moment we're about to implement: A MySQL master-master replicated HA cluster, 2 nodes with HA and ldirectord/LVS load-balancing. 2 x 3 node Apache Tomcat clusters with HA and load-balancing of clones in slightly different configs. A 2 node HA web server cluster with DRBD (so active/passive, no clones) These projects are very important to our business and we're really impressed with how it all works. We have a base config in mind now with every solution we look at so anything we host can just be run as a load-balanced cloned resource on SLES 11 HAE using ldirectord/LVS/Pacemaker and AIS. > -----Original Message----- > From: [email protected] [mailto:linux-ha- > [email protected]] On Behalf Of David Hoskinson > Sent: 25 June 2009 14:33 > To: General Linux-HA mailing list > Subject: Re: [Linux-HA] Failover problem > > Dude, you have this stuff down don't you.... So far it is all working. > Doing > testing of various "down" states now such as reboot, pulled power, pulled > network cable. I would like to thank you for your help with this. > > > On 6/25/09 3:30 AM, "[email protected]" > <[email protected]> wrote: > > > Oops sorry that's meant to be no-quorum-policy="ignore" > > > >> -----Original Message----- > >> From: [email protected] [mailto:linux-ha- > >> [email protected]] On Behalf Of [email protected] > >> Sent: 25 June 2009 09:22 > >> To: [email protected] > >> Subject: Re: [Linux-HA] Failover problem > >> > >> Just set up SSH STONITH until you can get something more concrete in. > >> You really have to use STONITH no matter what. Create an SSH RSA/DSA > > key > >> without a password so you can SSH as root from one server to the other > >> without it asking for a password, then just: > >> > >> crm configure > >>> primitive ssh-stonith stonith:ssh params hostlist="host1 host2" op > >> monitor interval=1h > >>> clone stonith-clone ssh-stonith > >>> commit > >> > >> Good doc: > >> http://www.clusterlabs.org/mediawiki/images/f/f2/Crm_fencing.pdf > >> > >> To set the quorum policy to ignore is simply: > >> > >> crm configure property no-quorum-policy=ignore > >> > >> For a 2-node cluster I generally set the following as default: > >> > >> no-quorum-policy="stop" \ > >> start-failure-is-fatal="false" \ > >> stonith-action="reboot" \ > >> > >>> -----Original Message----- > >>> From: [email protected] [mailto:linux-ha- > >>> [email protected]] On Behalf Of David Hoskinson > >>> Sent: 24 June 2009 21:45 > >>> To: General Linux-HA mailing list > >>> Subject: Re: [Linux-HA] Failover problem > >>> > >>> Im sorry this is maybe where my knowledge is lacking. I don't have > >> the > >>> hardware for a third node, but I understand your reasoning.... > >>> > >>> Don't understand how to add stonith and haven't found a good > > document > >> for > >>> that... I also get No STONITH resources have been defined when I do > > a > >>> crm_verify -LV > >>> > >>> Don't know how to set quorom policy to ignore. > >>> > >>> Which of the last 2 would you suggest, and where to look for info on > >> how > >>> to > >>> do it. > >>> > >>> thanks > >>> > >>> > >>> On 6/24/09 3:26 PM, "Lars Ellenberg" <[email protected]> > >> wrote: > >>> > >>>> On Wed, Jun 24, 2009 at 02:05:46PM -0500, David Hoskinson wrote: > >>>>> System running 2.99 heartbeat and pacemaker 1.04. Running fine > > in > >>> master > >>>>> slave mode. However if I shut down the slave server, all the > >> services > >>> stop > >>>>> on the master until the slave comes back up, does the election > > and > >> once > >>>>> again starts the services on the master. This doesn't seem to be > >> the > >>> way it > >>>>> should be. Same thing if I shut the master down. Services go > > off > >> line > >>>>> until master is back up. > >>>> > >>>> Two node cluster, one vote down, > >>>> 50% is NOT majority -> single node has no quorum. > >>>> Quorum policy probably says: no quorum -> stop. > >>>> You need to > >>>> - add more nodes (just to have a real quorum), and/or > >>>> - add stonith, and/or > >>>> - set quorum policy to ignore. > >>> > >>> > >>> _______________________________________________ > >>> 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 > > > _______________________________________________ > 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
