On Thu, Apr 29, 2010 at 7:37 PM, mike <[email protected]> wrote: > Hello all, > > We had a simple 2 node MySQL cluster - nothing special. One instance > that worked perfectly. We recently added 3 instances and now we're > having some issues. The problem is that Heartbeat issues a MySQL Status > immediately after the MySQL Start .. and of course the MySQL Status will > fail given that the instances are still coming up .
The start operation should not return until MySQL is fully up. Is this an LSB or OCF script? > Then I see a MySQL > stop, followed by another start and then a status. So we get into this > MySQL Status / Stop / Start loop and it's not pretty. Is there a > setting somewhere that I can change that will allow MySQL to do a start, > wait fro say 30 seconds and THEN issue the status? > > Thanks > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
