[Pacemaker] MySQL-Cluster with Pacemaker

[Stallmann, Andreas]

Well, yes, I read the presentation a while ago, but it didn't present me with any new information.

What Florian does is replicate a MySQL-Master over two nodes with DRBD and have several MySQL-Slaves replicate their data from the current Master via the built-in mechanism.

That's firstly quite nice, if you have a scenario, where there is the need for multiple nodes to be read from and where one single node for writing is sufficient.

Secondly, this scenario works only with 2+(n>1) nodes, whereas we have (and want) a classical 2 node scenario.

Thirdly (and that's the main issue with MySQL on DRBD), the failover process still takes quite long, because of the amount of events due to happen: Stop mysql on node 1, unmount the filesystem, switch DRBD master/slave, mount filesystem on node 2, start mysql (and perhaps repair tables).

Still, thanks for the suggestion.

Cheers,

Andreas



-----------------------------
CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef.
Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136)
Geschäftsführer/Managing Directors: Anke Höfer
-----------------------------

-----Ursprüngliche Nachricht-----
Von: Andreas Kurz [mailto:andreas at hastexo.com]
Gesendet: Mittwoch, 1. Februar 2012 23:55
An: pacemaker at oss.clusterlabs.org
Betreff: Re: [Pacemaker] MySQL-Cluster with Pacemaker

Hello,

On 01/30/2012 10:46 AM, Stallmann, Andreas wrote:
> Hi!
>
>
>
> I'm on the lookout for alternatives to our current MySQL "cluster",
> which is an Active/Standby solution with MySQL on DRBD.
>
> With increasing customer demand for a faster failover, we want an
> Active/Passive or even an Active/Active cluster.

Already had a look at this presentation my colleague Florian held at Percona Live UK 2011 in London?

http://goo.gl/5mDFR

Regards,
Andreas

--
Need help with Pacemaker?
http://www.hastexo.com/now

>
>
>
> Currently we run a Tomcat application, which works in
> Active/Passive-Mode. The applications on the active node communicate
> it's status via a MySQL database to the passive node. In our current
> setup, both nodes run the tomcat application but only one holds the
> database (due to the setup with DRBD). For faster failovers, we'd
> rather want the database to be active on both nodes. It's not
> necessary, that it can written on both nodes, but read access would be
> desirable. The thought is, that switching the "master status" of a
> database might be quicker than switching DRBD's master status,
> unmounting and mounting the file system and stopping and starting the database.
>
>
>
> A MySQL/Pacemaker cluster with replication as described  in
> http://www.mysqlperformanceblog.com/2011/11/29/percona-replication-man
> ager-a-solution-for-mysql-high-availability-with-replication-using-pac
> emaker/  thus looked very promising, but it seems to be not yet mature
> enough for a production environment. Please do correct men if I'm
> wrong there, I'm really interested in your experience with this
> solution in a real world scenario.
>
>
>
> Are there perhaps other howtos describing Pacemaker and MySQL replication?
>
>
>
> The second idea was using the native MySQL NDB clustering with
> Pacemaker.
> http://www.mysqlperformanceblog.com/2010/05/19/pacemaker-please-meet-n
> db-cluster-or-using-pacemakerheartbeat-to-start-a-ndb-cluster/
> (from 2010, uses heartbeat and pacemaker) and
> http://www.howtoforge.com/loadbalanced_mysql_cluster_debian (from
> 2008, uses pure heartbeat). Are there any more recent "howtos" on
> pacemaker and MySQL NDB 7.x describe this. Can you provide me with
> your opinions and field reports on these setups?
>
>
>
> Looking forward to your upcoming mails,
>
>
>
> Andreas
>
>
>
>
>
>
>
>
>
>
>
>
>
> ----------------------------
> CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef.
> Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr.
> 9136) Geschäftsführer/Managing Director: Anke Höfer
>
>  ----------------------------
>
>
>
>
>
> _______________________________________________
> 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://bugs.clusterlabs.org