On 4/13/07, Piotr Kaczmarzyk <[EMAIL PROTECTED]> wrote:
> When I tested second version of the script the resource that failed to start
> stayed on the node all the time and failcount increased. By changing
> "default-resource-stickiness" and "default-resource-failure-stickiness"
> parameters I was be able to force it to move to another node after a number
> of failures.
I just tested that setup more: I set default-resource-failure-stickiness
to -100 and added preferrence constraints for each of two squids - first
squid had preferrence 500 to run on first node, second had 500 to run on
second node.
After 6 failures squid from node 1 was moved to node 2. That's correct.
But after a failure on node 2 that squid disappeared. Why? Because it's
score on both nodes was negative (node1: 500-6*100 = -100, node2:
0-1*100 = -100)?
thats usually the reason (though I don't know for sure the exact scores)
Best regards,
Piotr
_______________________________________________
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
