On Thu, Dec 10, 2009 at 1:39 PM, Kamran Hanif <[email protected]> wrote: > Hi Andrew > > Thankx very much for your suggestion. > I have just checked that from Linux-ha website and I found those to be the > latest. > heartbeat-2.0.8-2.el4.centos.i386.rpm 12-Feb-2007 22:10 1.9M > heartbeat-gui-2.0.8-2.el4.centos.i386.rpm 12-Feb-2007 22:10 > 129K > heartbeat-ldirectord-2.0.8-2.el4.centos.i386.rpm 2-Feb-2007 22:10 > 111K > heartbeat-pils-2.0.8-2.el4.centos.i386.rpm 12-Feb-2007 22:10 130K > heartbeat-stonith-2.0.8-2.el4.centos.i386.rpm 12-Feb-2007 22:10 230K > > Can you please see if it is correct?
its not. as I said, you need pacemaker: http://www.clusterlabs.org/wiki/Install > Have you got any sample config for 4 servers cluster according to the > arrangements stated. no > > Cheers, > Kamran > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Andrew Beekhof > Sent: 10 December 2009 12:16 > To: General Linux-HA mailing list > Subject: Re: [Linux-HA] 4 Servers heartbeat cluster > > 2009/12/10 Kamran Hanif <[email protected]>: >> Hi Sharfuddin, >> >> >> >> Thanks very much for your reply. >> >> I can’t see any problem with your English. >> >> I have not done much work in Linux and heartbeat before apart from building >> the two servers heartbeat cluster. >> >> Can you please tell me exactly what file needs to be changing? >> >> What configuration we need to put in ha.cf and haresource? > > You'll need to use a newer version of heartbeat and pacemaker on top. > The resource manager in heartbeat isn't capable of handling more than 2 nodes. > >> >> I’m using RHEL4.7 and heartbeat‐2.0.8‐2.el4. > > > >> >> >> >> Cheers, >> Kamran >> >> >> >> _____ >> >> From: Muhammad Sharfuddin [mailto:[email protected]] >> Sent: 08 December 2009 18:02 >> To: [email protected] >> Cc: [email protected] >> Subject: Re: [Linux-HA] 4 Servers heartbeat cluster >> >> >> >> >>>--- On Tue, 12/8/09, Kamran Hanif <[email protected]> wrote: >>> The switchover scenario should be such that if Node 1 fails at site 1, >> Node >>> 2 will take over as master and if both Node 1 and Node 2 fail then Node 3 >>> should take over as Primary. >>> >> its quite easy, just create the location rule for each resource, >> and define the max score for node1(site1), and respectively >> for all nodes(highest score for node1, and lowest score for node4) >> . >>> If Node 1 comes back up again it will resume its primary >>> state again. >> I am sure its default(at least for Heartbeat V2), because by default, >> resource stickiness is not defined. >> >> sorry for my bad english ;( >> >> Regards, >> Muhammad Sharfuddin >> >> >> >> _______________________________________________ >> 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
