Overview of Galera Cluster¶
Galera Cluster is a synchronous multi-master database cluster, based on synchronous replication and MySQL and InnoDB. When Galera Cluster is in use, database reads and writes can be directed to any node. Any individual node can be lost without interruption in operations and without using complex failover procedures.
At a high level, Galera Cluster consists of a database server (i.e., MySQL or MariaDB) that uses the Galera Replication Plugin to manage replication. To be more specific, the MySQL replication plugin API has been extended to provide all the information and hooks required for true multi-master, synchronous replication. This extended API is called the Write-Set Replication API, or wsrep API.
Through the wsrep API, Galera Cluster provides certification-based replication. A transaction for replication, the write-set not only contains the database rows to replicate, but also includes information on all of the locks that were held by the database during the transaction. Each node then certifies the replicated write-set against other write-sets in the applier queue. The write-set is then applied—if there are no conflicting locks. At this point, the transaction is considered committed, after which each node continues to apply it to the tablespace.
This approach is also called virtually synchronous replication, given that while it is logically synchronous, the actual writing and committing to the tablespace happens independently, and thus asynchronously on each node.
Benefits of Galera Cluster
Galera Cluster provides a significant improvement in high-availability for the MySQL system. The various ways to achieve high-availability have typically provided only some of the features available through Galera Cluster, making the choice of a high-availability solution an exercise in trade-offs.
The following features are available through Galera Cluster:
True Multi-Master
You can read and write to any node at any time. Changes to data on one node will be replicated on all.
Synchronous Replication
There is no slave lag, so no data is lost if a node crashes.
Tightly Coupled
All nodes hold the same state. There is no diverged data between nodes.
Multi-Threaded Slave
This allows for better performance and for any workload.
No Master-Slave Failover
There is no need for master-slave operations or to use VIP.
Hot Standby
There is no downtime related to failures or intentionally taking down a node for maintenance since there is no failover.
Automatic Node Provisioning
There’s no need to backup manually the database and copy it to the new node.
Supports InnoDB.
The InnoDB storage engine provides for transactional tables.
Transparent to Applications
Generally, you won’t have to change an application that will interface with the database as a result of Galera. If you do, it will be minimal changes.
No Read and Write Splitting Needed
There is no need to split read and write queries.
In summary, Galera Cluster is a high-availability solution that is both robust in terms of data integrity and provides high-performance with instant failovers.
Cloud Implementations with Galera Cluster
An additional benefit of Galera Cluster is good cloud support. Automatic node provisioning makes elastic scale-out and scale-in operations painless. Galera Cluster has been proven to perform extremely well in the cloud, such as when using multiple small node instances, across multiple data centers—AWS zones, for example—or even over Wider Area Networks.
