[Pacemaker] resource could not migrate back
Robert van Leeuwen
vanleeuwen at stone-it.com
Mon Feb 14 07:58:32 UTC 2011
> I have two node ha cluster node1 and node2 I start virtual IP resource in
> cluster on node1, I set stick-ness=0,when node1 reboot virtual ip migrate to
> node2.however when node1 come back virtual IP still start on node2.Is there any
> way to migrate resource back to node1?
If you want auto-failback to a specific node you have to set the preference of a resource to a node.
e.g.
crm configure location location-resource1 resource1 100: node1
If the difference between this location preference and the node that it is running on is higher than the cluster suite stickiness it will migrate the resource.
The stickiness off the cluster suite is set as follows:
crm_attribute --type rsc_defaults --attr-name resource-stickiness --attr-value 50
Regards,
Robert van Leeuwen
More information about the Pacemaker
mailing list