y.trudeau at videotron
Aug 1, 2012, 5:15 PM
Post #3 of 3
my answers are embedded.
Le 2012-07-18 09:24, DENNY, MICHAEL a écrit :
> Our current monitor action tests the availability of the mysql database. However, the monitor fails if mysql is doing recovery processing. And the recovery processing can take a long time. Do you know if there is a way to programmatically determine if mysql is in recovery mode (and is processing the log entries)? or some existing utility prog that can report that mysql is started but in recovery mode? I want to update the monitor action to succeed if in recovery mode.
There's no straightforward way but that would be useful. Same when
stopping when there's a large number of innodb pages to flush. I'll see
what could be done and if there's a solution, I'll submit a patch to at
least the Percona version of MySQL (I work there).
> - We using mysql on Ubuntu servers using heartbeat/pacemaker in an Active/Passive redundant pair configuration.
> - When simulating failover, we have observed that the start action on the new server will succeed, exit almost immediately, although mysql has actually begun recovery processing and subsequent "service mysql status" reports that it is not available for use.
> - Our current monitor action fails if mysql is not available for use.
> Thanks for the help,
> Pacemaker mailing list: Pacemaker [at] oss
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
Pacemaker mailing list: Pacemaker [at] oss
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf