Hi'
If you use the cib.xml approach, then
http://linux-ha.org/ha.cf explicitly states the following.
"...NOTE: auto_failback does not have any effect on a
Release 2 CRM-style cluster (one configured with crm on).
For CRM-style clusters, this has been replaced with the
default_resource_stickiness attribute in the CIB...."
I hit that problem myself recently when upgrading from v1
to v2. The following section in my cib.xml cured the
problem.
<crm_config>
<cluster_property_set>
<attributes>
<nvpair id="default-resource-stickiness"
name="default-resource-stickiness" value="INFINITY"/>
</attributes>
</cluster_property_set>
</crm_config>
Best regards.
Thomas.
--- Jochen Lienhard <[EMAIL PROTECTED]> skrev:
> I'm using the configuration
>
> autofailback off
>
> If I undestand right, the node, who own the ressources
> should keep them
> until it goes down.
>
> But it does not work so.
>
> If I send node1 to standby, node2 takes all ressources,
> but when I
> activate node1 again, it
> steals all ressources from node2.
>
> I'm using HA 2.1.2 .... is the value 'off' perhaps not
> longer supported,
> should I use FALSE or False or false instead? ;-)
>
> Or is there another configuration point, that I have
> missed.
Trænger du til at se det store billede? Kelkoo giver dig gode tilbud på
LCD TV! Se her http://dk.yahoo.com/r/pat/lcd
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
