/ 5.6. Specifying Resource Failover Nodes | ||||
|---|---|---|---|---|
 | 5.5. Configuring Resource Constraints | 5.7. Specifying Resource Failback Nodes (Resource Stickiness) |  | |
/ 5.6. Specifying Resource Failover Nodes | ||||
|---|---|---|---|---|
| 5.5. Configuring Resource Constraints | 5.7. Specifying Resource Failback Nodes (Resource Stickiness) | | |
To determine a resource failover, use the meta attribute migration-threshold. For example:
crm(live)configure# location r1-node1 r1 100: node1Normally r1 prefers to run on node1. If it fails there, migration-threshold is checked and compared to the failcount. If failcount >= migration-threshold then it is migrated to the node with the next best preference.
Start failures set the failcount to INFINITY depends on the
start-failure-is-fatal option. Stop failures cause
fencing. If there's no STONITH defined, then the resource will not
migrate at all.
