CC'ing the mailing list because the previous request to conduct configuration questions there was ignored.

Had it been sent there in the first place, one of the many people there would probably have answered the question by now. Why I need to explain this concept to the project leader is a mystery to me.


On Oct 30, 2007, at 2:44 AM, Alan Robertson wrote:

Hi,

I've been working with a customer - trying to get them up and running on version 2.1.2. I got everything to work except for one thing: They require that their web server fail over on the 3rd failure. I read the documentation on the failcount stuff on the web site here: http://www.linux-ha.org/v2/faq/forced_failover

I think I understood it, and I created a CIB to match. In the CIB I created, I believe it should fail over on the 3rd failure. In practice it fails over reliably on the 9th iteration instead. We had been doing a "killall httpd" to fail the web server.

9th is correct.

As has been explained here on the list a number of times, the group's stickiness is N * default-resource-stickiness, where N is the number of resources in the group.

Including the rsc_location constraint, the group stickiness is therefor: 4 * 20 + 1 = 81 So clearly apache is going to need to fail 9 times (9 * default- resource-failure-stickiness = -90) before the group is moved.


Of course it all starts getting even more complicated when one starts creating rsc_colocation constraints with other groups and primitives.


Looking at the ptest output, it appears that the failures are accruing points to the wrong resource. The resource we were failing was a web server, and the resource that ptest seems to indicate is accruing failure points is the ip address (immediately before it in the group), and NOT the web server.

Off hand, this sounds a bit like a bug to me. I've attached the relevant files - the output of cibadmin -Q, a spreadsheet with the output of the various ptest runs, and the logs from both machines in the clusters.

Of course, if I just misunderstood or misconfigured something instead, or if it's already fixed, then by all means let me know.

        Thanks In Advance!


_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to