China wrote:
Ok, I've set resource_stickiness to 150, a score of 100 to the default node
PC_A and a score_attribute for pingd. Now the resource when fail doesn't
start on PC_B. Why?
The way I understand you, and please correct me or post your current
cib.xml, is:
pingd multiplier: 200 (as suggested by Andrew)
one ping node
a constraint with score 100 for node test-ppc
resource-stickiness = 150
So this would make a startup score for your group_1:
node test-ppc: 100 (constraint) + 200 (pingd with one ping node) = 300
node test3: 200 (pingd with one ping node) = 200
So now the resource will run on node test-ppc and its score increases to
450 due to the 150 resource-stickiness.
Then you fail test-ppc (what exactly do you do again?).
So you have only a score of 200 for node test3 (no other nodes
available). Now the resource will run there and have 150 added to its
score. So test3 should end up with a score of 350.
If test-ppc comes back, it will have 300 again (propably), so the
resource should stay in place.
Oh, wait a minute. I just re-read your initial mail. Are you only using
one connection between your nodes and unplug that connection to force a
failure? That's forced to fail and you do not have STONITH.
I think that's the first thing you should fix.
Regards
Dominik
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
