First of all, thanks for the speedy reply. > From: "Andrew Beekhof" <[EMAIL PROTECTED]> > > On Sun, Jul 27, 2008 at 15:21, Itay Donenhirsch <[EMAIL PROTECTED]> wrote: > > Hi all, > > I have a weird problem: > > > > There are 4 nodes: ha1 ha2 ha3 ha4 > > There are 3 resource groups: Gha1 Gha2 Gha3 > > The cluster is symmetric. > > Upon startup - Gha1 lives on ha2, Gha2 lives on ha3 and Gha3 lives on ha4. > > > > I do a 'service heartbeat stop' on ha3. I expected to see Gha2 migrate from > > ha3 to ha1 but instead I get that Gha2 migrates to ha2 and Gha1 migrates to > > ha1. Why is that? > > Because you didnt tell it you cared.
I don't think you understood me correctly, maybe I didn't make myself clear enough, sorry. I don't want the resources to fail in a specific order, just in such a way that will not make non-failed resources switch nodes. I don't care which node gets the failed resource as long as it will be done in the minimal number of fail-overs. It seems to me that it should have worked using symmetric cluster and no location constraints at all. > > Read up on rsc_location constraints in: > http://clusterlabs.org/mw/Image:Configuration_Explained.pdf > Assuming you did get me right, where in the document is this explained? What words should I look for? > > > > Another question - is there any way to set the initial location of each > > resource? > > see above > > > i.e. on each node will each resource is located upon initial > > cluster > > configuration (cibadmin -R -x ...)? > > > > Attached is a report.tar.gz generated by hb_report. > > Thanks Itay Donenhirsch [EMAIL PROTECTED] _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
