On Wed, Sep 21, 2011 at 09:14:45AM -0400, Yves Trudeau wrote: > Hi, > > On Tue, 2011-09-20 at 18:06 +0200, Dejan Muhamedagic wrote: > > Hi, > > > > On Tue, Sep 20, 2011 at 11:16:39AM -0400, Yves Trudeau wrote: > > > Hi, > > > the whole resource agent script is available here: > > > > > > https://code.launchpad.net/percona-prm > > > > Is that in any way related to the existing mysql RA? > > It is not. The existing MySQL is inadequate for replication and > unusable with any non-trivial load. I had a discussion with Florian a > few months ago about it. Basically if a slave lags behind, killing it > will do no good. The RA I am writing deal _only_ with replication and > the associated logic.
Can this be integrated into the existing mysql RA, or do you think it really should be two seperate RA, even in the long term? > > > In order to make thing easier to follow I added the return codes of the > > > agent to the lrmd log. > > > > > > Sep 15 16:54:08 testvirtbox1 lrmd: [30902]: info: > > > rsc:p_MySQL_replication:0:6: probe exit 0 > > > Sep 15 16:54:09 testvirtbox1 lrmd: [30902]: info: > > > rsc:p_MySQL_replication:0:7: promote exit 0 > > > Sep 15 16:54:12 testvirtbox1 lrmd: [30902]: info: > > > rsc:p_MySQL_replication:0:12: demote exit 0 > > > Sep 15 16:54:12 testvirtbox1 lrmd: [30902]: info: > > > rsc:p_MySQL_replication:0:14: demote exit 0 > > > Sep 15 16:54:13 testvirtbox1 lrmd: [30902]: info: > > > rsc:p_MySQL_replication:0:15: stop exit 0 > > > Sep 15 16:54:13 testvirtbox1 lrmd: [30902]: info: > > > rsc:p_MySQL_replication:0:19: start exit 0 > > > Sep 15 16:54:14 testvirtbox1 lrmd: [30902]: info: > > > rsc:p_MySQL_replication:0:20: promote exit 0 > > > Sep 15 16:54:17 testvirtbox1 lrmd: [30902]: info: > > > rsc:p_MySQL_replication:0:25: monitor exit 8 > > > > > > What I don't understand is why there is no "monitor" call after the > > > first promote at 16:54:09. Maybe you should just wait a little longer? > > There is and it's called probe. Probe is a monitor with interval > > set to 0. > > I know about probe... If you read my question, I am asking why there no > monitor _after_ the promote. probe is the first method on the script > after pacemaker start. Basically I want to know why there is a demote > after the promote when the promote returned success. Do you have two monitor operations, one for each role, with *different* intervals? The intervals really need to be different. op monitor role=Master interval=59s timeout=30s \ op monitor role=Slave interval=60s timeout=30s BTW, do you also want to use notifications in some way? > > Thanks, > > > > Dejan > > > > > > > > Regards, > > > > > > Yves > > > > > > > > > On Tue, 2011-09-20 at 17:27 +0300, Dan Frincu wrote: > > > > Hi, > > > > > > > > On Tue, Sep 20, 2011 at 4:36 PM, Yves Trudeau <[email protected]> > > > > wrote: > > > > > Hi, > > > > > I am currently developing a master-slave resource agent to handle > > > > > MySQL replication in a sane way. So far, the resource agent works > > > > > relatively well but I have this strange behavior when promoting a > > > > > node. > > > > > The excerpt below is when a single node is started, look at the > > > > > promote > > > > > -> demote -> promote sequence. From the trace of my resource agent > > > > > script, evertything seems alright regarding returns code. Any idea > > > > > why > > > > > this behavior. > > > > > > > > > > > > > Without the actual resource agent I'd say it's easier to speculate and > > > > harder to troubleshoot. > > > > > > > > > Sep 15 16:54:08 testvirtbox1 lrmd: [30902]: info: > > > > > rsc:p_MySQL_replication:0:6: probe > > > > > Sep 15 16:54:09 testvirtbox1 lrmd: [30902]: info: > > > > > rsc:p_MySQL_replication:0:7: promote > > > > > Sep 15 16:54:12 testvirtbox1 lrmd: [30902]: info: > > > > > rsc:p_MySQL_replication:0:12: demote > > > > > Sep 15 16:54:12 testvirtbox1 lrmd: [30902]: info: > > > > > rsc:p_MySQL_replication:0:14: demote > > > > > Sep 15 16:54:13 testvirtbox1 lrmd: [30902]: info: > > > > > rsc:p_MySQL_replication:0:15: stop > > > > > Sep 15 16:54:13 testvirtbox1 lrmd: [30902]: info: > > > > > rsc:p_MySQL_replication:0:19: start > > > > > Sep 15 16:54:14 testvirtbox1 lrmd: [30902]: info: > > > > > rsc:p_MySQL_replication:0:20: promote > > > > > Sep 15 16:54:17 testvirtbox1 lrmd: [30902]: info: > > > > > rsc:p_MySQL_replication:0:25: monitor > > > > > > > > > > Regards, > > > > > > > > > > Yves -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
