Nikita Michalko wrote:
Hi all!
I have some troubles with HA V2.1.3 on SLES10 SP1, two-node cluster with 1
resource group=2 resources. Intended is forced failover of the group on the
third failure of any resource in the group; one node is preferred over the
other (see attached configuration).
After start are resources running on the preferred node (demo), as expected,
but with 1 failcount and with following score (script "showscores"):
Resource Score Node Stick. Failcount Fail.-Stickiness
IPaddr_193_27_40_57 0 dbora 2 0 -3
IPaddr_193_27_40_57 2 demo 2 0 -3
ubis_udbmain_13 -INFINITY dbora 2 0 -3
ubis_udbmain_13 INFINITY demo 2 1 -3
Score of the first resource (IPaddr_193_27_40_57) is 2 as expected (group
resource_stickiness=1) , but the second resource has score INFINITY -
why ? Because of added colocation constraint for group ?
In a colocated group (which is the default), all subsequent resources
are tied to the group's first resource with a score of INFINITY.
To not allow them to run on another node but the node the first resource
is run on, they also get -INFINITY for any other node.
Regards
Dominik
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
