Andrew, Thanks for the pointer - I was incorrectly trying to start the clone itself via crm_resource, not a specific instance of it. Specifying an ID of the clone works.
Is there a benefit to using master/slave in this case over using a basic clone? I have, perhaps erroneously, been planning to have every MySQL node be a master at all times (even when not being actively used) to simplify configuration. Jeremy On 7/18/07, Andrew Beekhof <beekhof at gmail.com> wrote: >> 1) Is it possible to manually restart a single instance of a clone >> resource? > > you tried crm_resource -C -r mysql:0 -H hostname ? > note the ":0" this is the way to address a specific clone instance > > > > > 2) Is there a way to have the "cleanup" bring the failed node back but > > *not* restart the active node? > > clone handling has been significantly improved in recent versions (and > even again since then), you might want to try grabbing the latest code > > > 3) Is there a better way to configure heartbeat to deal with multi-master > > MySQL? > > master/slave resources can have as many masters as you like > http://linux-ha.org/v2/Concepts/MultiState _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
