[Pacemaker] Circular replication help needed - how to make sure VIP runs on same node with a healthy mysql

[Michael Marrotte]

The current MySQL RA supports master/slaves which is great.  It would be
nice if it supported multiple masters.  If I have some free cycles, I'll
look into adding it.  I think lots of folks probably use DRBD b/c there's
no RA alternative and they have some experience with it.  When standing up
a new system and not having much experience with DRBD, I can understand why
there would be some apprehension to DRBD or anything else they might have
to add into the mix.  You're thinking here I have hardware, maybe some virt
OS, a linux guest, heartbeat, pacemaker, mysql (masters, slaves), a million
lines of code to write...  Now I need some more cluster management stuff
like DRBD?  What's DRBD and why doesn't my cluster stuff handle this common
MySQL master/master/salve use-case?  It definitely add value to an already
powerful MySQL RA.  When's it going to be ready? :)  Cheers!

~Mike


On Sun, Nov 6, 2011 at 9:34 AM, Florian Haas <florian at hastexo.com> wrote:

> On 2011-11-05 18:20, Attila Megyeri wrote:
> > Hello,
> >
> >
> >
> > I am having a hard time configuring a relatively simple mysql
> environment.
> >
> >
> >
> > What I’d like to achieve is:
> >
> > ·         One master and a slave, with replication
> >
> > ·         Relatively quick failover if the master node, or Mysql fail.
> >
> >
> >
> > I tried the Mysql cluster approach, but seemed to be too slow, and to
> > many limitations (foreign keys, triggers, views, etc).
> >
> >
> >
> > I decided to go with the Mysql replication.
>
> You want a simple 2-node MySQL cluster with failover? Why not go with
> DRBD then, as everyone else would in that situation?
>
> > Tried to use the mysql RA from clusterlabs 3.9.2 – but no luck,
> > replicaiton simply did not work out.
>
> Sorry to say this, but as a co-author of that agent I'll say that that's
> exactly the kind of feedback we strongly dislike, as it doesn't help us
> at all improving the agent, or its documentation. So,
>
> - What were you trying to achieve?
> - What was your configuration?
> - What went wrong?
> - What were you unable to fix?
>
> For the DRBD based approach (which I would highly recommend), do
> consider taking a look at
>
> http://www.hastexo.com/content/mysql-high-availability-sprint-launch-pacemaker
> .
> We'll be happy to provide you with the virtual images used in this
> tutorial, so you can set things up yourself in a cleanroom testing
> environment.
>
> Cheers,
> Florian
>
> --
> Need help with High Availability?
> http://www.hastexo.com/now
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20111106/624b13a1/attachment.htm>