On Mon, Jun 23, 2008 at 12:05, Adrian Chapela <[EMAIL PROTECTED]> wrote: > Andrew Beekhof escribió: >> >> On Thu, Jun 19, 2008 at 17:45, Adrian Chapela >> <[EMAIL PROTECTED]> wrote: >> >>> >>> Hello, in the past I have a problem with Pacemaker. This problem was a >>> inncesary suffling of master/slave resource >>> (http://developerbugs.linux-foundation.org/show_bug.cgi?id=1852). >>> >>> Now I can't do a failover. I started two heartbeat servers and the mysql >>> servers startup OK, heartbeat is OK and all constraints seems to be OK. >>> Then >>> I failed the master mysql server. Heartbeat detects the problem but It >>> doesn't do failover. If I stop the heartbeat, the result is the same. >>> >> >> So it was left as stopped? >> What failure stickiness are you using? >> > > This are the values: > <nvpair id="cib-bootstrap-options-default-resource-stickiness" > name="default-resource-stickiness" value="100"/> > <nvpair id="cib-bootstrap-options-default-resource-failure-stickiness" > name="default-resource-failure-stickiness" value="-100"/> > > One node is Started and failure node is in Failed. When I stop heartbeat on > a Master node, failover is done very well, but If a Master node failst, the > failover isn't done. > > Could be a bad RA ? Here is my master/slave RA: > http://code.adrianchapela.net/heartbeat/mysql_slave_master
it's possible but hard to say because i don't know which actions failed (did a start fail too?) or what the rest of the scoring looks like. its probably best if you create a hb_report and attach it to a new bugzilla. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
