Hi Dominik, Thank for your comment. > If the error occurs on the resource, then resouce-failure-stickiness > will come to play and make your scores: > Node1: 10 - 10 = 0 > Node2: 9 > As 9 > 0, the resource will be started on Node2, and 22 stickiness will > be added. So you have 31 > 0.
In your comments, you remarked a failover should occur if the following condition met. Node1_preference + Node1_failcount * failure_stickness < Node2_preference + Node2_failcount * failure_stickness Is my understanding correct? >> Score settings for ResourceFoo >> > Node1 regular preference : 10 >> > Node2 regular preference : 9 >> > default-resource-stickiness : 22 >> > default-resource-failure-stickiness : -10 >> > > > Initial start on Node1 because 10 > 9. > Node1 then gets 22 stickiness added. So 32 > 9. > >> > Under this configuration, ResourceFoo firstly starts on Node1. >> > And if an error occurs, it should restart on Node1. > > If the error occurs on the resource, then resouce-failure-stickiness > will come to play and make your scores: > Node1: 10 - 10 = 0 > Node2: 9 > As 9 > 0, the resource will be started on Node2, and 22 stickiness will > be added. So you have 31 > 0. > >> > I took a test to confirm the hypothesis, >> > But in fact, ResourceFoo failed over. > > Which is intended. I think you misunderstood > resource-failure-stickiness. It is per-node. > > Regards > Dominik > > ps. I wonder how readable this email will be as my mailclient horribly > screwed up while typing this. -- Takenaka Kazuhiro <[EMAIL PROTECTED]> _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
