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?
On Dec 6, 2007 11:17 AM, Dominik Klein <[EMAIL PROTECTED]> wrote: > China wrote: > > Ok, now it works, but when the PC_A returns up the resource doesn't > remains > > on PC_B and failback to PC_A. > > How can I configure to switch the first time to PC_B on PC_A failover, > but > > not return back if PC_A returns UP? > > Set resource stickiness to a reasonable value. > > Here's roughly how stickiness works: > > When you startup, the scores are calculated from your constraints and a > decision is made where to run the resource (PC_A in your case). > Afterwards, the stickiness is added to the score for PC_A because the > resource is running there. > > Now PC_A fails. The node with the highest score for your resource gets > to run it (PC_B). After a successful start, the stickiness is added to > the score for PC_B. > > Now PC_A comes back. It will get its normal score from your constraints, > but no stickiness because the resource is not running there. > > So if you make (PC_B score + stickiness) > (PC_A score), the resource > will stay on PC_B. > > Regards > Dominik > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > -- Davide Belloni _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
