Hi, knowing that res1-[1-3] are in group-1 and res2-[1-3] are in group-2, the crm_verify -LVVVV 2>&1 | grep stick displays:
debug: unpack_config: Default stickiness: 5000 debug: common_apply_stickiness: Resource clone-1:0: preferring current location (node=node2, weight=1) debug: common_apply_stickiness: Resource res1-1: preferring current location (node=node2, weight=5000) debug: common_apply_stickiness: Resource res1-2: preferring current location (node=node2, weight=5000) debug: common_apply_stickiness: Resource res1-3: preferring current location (node=node2, weight=5000) debug: common_apply_stickiness: Resource clone:1: preferring current location (node=node3, weight=1) debug: common_apply_stickiness: Resource res2-1: preferring current location (node=node3, weight=5000) debug: common_apply_stickiness: Resource res2-2: preferring current location (node=node3, weight=5000) debug: common_apply_stickiness: Resource res2-3: preferring current location (node=node3, weight=5000) but I don't know how to make conclusions of this information ... Alain De : Dan Frincu <[email protected]> A : General Linux-HA mailing list <[email protected]> Date : 03/08/2011 13:28 Objet : Re: [Linux-HA] location and orders : Question about a behavior ... Envoyé par : [email protected] Hi, On Wed, Aug 3, 2011 at 2:22 PM, <[email protected]> wrote: > Hi & Thanks > > I don't think the 1000 or 5000 value makes any difference, The values make little difference, it's about having a higher score atm. > so the rsc_options could make it work ? Yes, I believe so. > But do you have also the order with a clone ? No. > Because on other of my configurations, I have also > property $id="cib-bootstrap-options" \ > default-resource-stickiness="5000" > and the resource does not failback automatically ... so ... > Could somebody explain ? Try the following: crm_verify -LVVVV 2>&1 | grep stick And see what scores (weights) are given to resources. Based on these weights it might make more sense. HTH, Dan > Thanks > Alain > > > > De : Dan Frincu <[email protected]> > A : General Linux-HA mailing list <[email protected]> > Date : 03/08/2011 13:00 > Objet : Re: [Linux-HA] location and orders : Question about a behavior ... > Envoyé par : [email protected] > > > > Hi, > > On Tue, Aug 2, 2011 at 6:06 PM, <[email protected]> wrote: >> Hi >> >> I have this simple configuration of locations and orders between > resources >> group-1 , group-2 and clone-1 >> (on a two nodes ha cluster with Pacemaker-1.1.2-7 /corosync-1.2.3-21) : >> >> location loc1-group-1 group-1 +100: node2 >> location loc1-group-2 group-2 +100: node3 >> >> order order-group-1 inf: group-1 clone-1 >> order order-group-2 inf: group-2 clone-1 >> >> property $id="cib-bootstrap-options" \ >> dc-version="1.1.2-f059ec7ced7a86f18e5490b67ebf4a0b963bccfe" \ >> cluster-infrastructure="openais" \ >> expected-quorum-votes="2" \ >> stonith-enabled="true" \ >> no-quorum-policy="ignore" \ >> default-resource-stickiness="5000" \ > > I use it as: > rsc_defaults $id="rsc-options" \ > resource-stickiness="1000" > Instead of: > property $id="cib-bootstrap-options" \ > default-resource-stickiness="5000" > And the behavior is the expected one, no failback. > > HTH, > Dan > >> >> (and no current cli- preferences) >> >> When I stop the node2, the group-1 is well migrated on node3 >> But when node2 is up again, and that I start Pacemaker again on node2, >> the group-1 automatically comes back on node2 , and I wonder why ? >> >> I have other similar configuration with same location constraints and > same >> default-resource-stickiness value, but without order with a clone >> resource, >> and the group does not come back automatically. But I don't understand > why >> this order constraint would change this behavior ... >> >> Thanks for your help >> Alain Moullé >> >> _______________________________________________ >> Linux-HA mailing list >> [email protected] >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems >> > > > > -- > Dan Frincu > CCNA, RHCE > _______________________________________________ > 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 > -- Dan Frincu CCNA, RHCE _______________________________________________ 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
