Galera Cluster: Synchronous Multi-Master Replication for MySQL HA

Finally I’ve decided to publish the slides about Galera Cluster that I’ve presented twice, at the internal Trivadis TechEvent conference past April and at the Linux Day 2013.

They are a little dated since the new Galera library 3.0 is out and it supports MySQL 5.6.

Hope you find them interesting.

Cheers

Ludovico

The following two tabs change content below.

Ludovico

Oracle ACE Director and Computing Engineer at CERN
Ludovico is an Oracle ACE Director, frequent speaker and community contributor, working as Computing Engineer at CERN, the European Organization for Nuclear Research, in Switzerland.

3 thoughts on “Galera Cluster: Synchronous Multi-Master Replication for MySQL HA

  1. We’ve installed Galera cluster in our organization. Do you suggest it for production? How do we compare this with Mysql Cluster NDB in terms of scalability? How do you handle similar applications (Drupal/Lamp/Redcap)? We had multilpe Drupal applications around. How can we consildate them with Galera?

  2. Hi Ramki,
    LOL, you’re also administering all the major RDBMS platform if I understand well 🙂

    Briefly, YES, if I suggest Galera for consolidation (I would go for Percona Cluster) even if I’ve never done it on a busy production. I’ve implemented it on 5.5 release, I know that new 5.6 patched servers are coming.
    From the database and hardware point of view is much simpler to administer compared to other solutions like Oracle RAC or MySQL cluster, but you have to plan it carefully at VIP and load balancing level. Especially if you have the hotspots I’ve described in my slides, a VIP for each application pointing to different single servers would allow to avoid the problem.
    Also, take care that the traditional LB doesn’t detect if a server isn’t available because the port 3306 (or whatever) will be available.

    Compared to MySQL Cluster, the main advantage is that Galera uses innoDB. the NDB engine is not always compatible with the applications, it’s most suitable for applications developed in-house (IMHO).

    cheers

    Ludovico

  3. Great, thanks. We are large organization with all flavours of rdbms. We have very good infrastructure with site licenses fot software. RAC is not yet implemented because of complexity to maintain and I also feel it may not be a right tool for consolidation of non critical databases where availability is of secondary concern. We can achieve OS level availability with VMware. Exadata is the preferred for consolidation, cost and maintennace are too high.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.