On Wed, Feb 9, 2011 at 9:05 AM, Erik Dobák <erik.do...@gmail.com> wrote: > i have 2 nodes which are running 2 resource groups in an active/passive > cluster. my goal was to run 1 resource active on lc-cl1 and the other > resource on node lc-cl2. > > this is how i configured it: > > group bamcluster ipaddr2 lcbam \ > meta target-role="Started" is-managed="true" > group bamclusteruat ipaddr2uat lcbamuat > > location primarylc bamcluster 100: lc-cl1 > location primarylcuat bamclusteruat 100: lc-cl2 > location secondarylc bamcluster 50: lc-cl2 > location secondarylcuat bamclusteruat 50: lc-cl1 > rsc_defaults $id="rsc-options" \ > resource-stickiness="75" > > but after adding the second resource (bamclusteruat) did also try to start > at lc-cl1
of course, both resources prefer that host the most. only if primarylcuat is down will they run elsewhere. > > what did i mess up? check up on colocation constraints (with a negative score) > > E > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
