Join us for an in-depth webinar where we introduce the new Helm Chart for Galera Cluster for MySQL, now available from Codership (read the blog).

In this session, we’ll guide you through the process of deploying a high-availability MySQL cluster using Galera Cluster on Kubernetes (live demo!). You’ll learn how Helm Charts can simplify Kubernetes application management, including installation and upgrades, while ensuring robust deployment automation.

This webinar is ideal for database administrators, DevOps engineers, and anyone looking to streamline their MySQL high availability deployments on Kubernetes, whether on cloud platforms like Amazon EKS, Google GKE, or on-premises solutions. We’ll cover best practices for configuration, deployment, and scaling of your Galera Cluster, and offer insights on how to …

Codership, the makers of Galera Cluster, are pleased to announce the availability of Helm charts for Galera Cluster for MySQL 8.0.39. It is available on our GitHub releases page, for convenience. You are encouraged to send feature requests at our GitHub issues.

Helm charts help you manage your Kubernetes applications, to install and upgrade any Kubernetes applications; think of it as a package manager. Kubernetes helps you automate the deployment, management and scaling of containerized applications.

For this blog post, we will use the example of setting it up at DigitalOcean, but the setup is similar, whether you do this in a …

Galera Cluster Enterprise Edition (EE) has had support for Non-Blocking Operations (NBO) schema upgradesever since the first release of Galera Cluster Enterprise Edition (EE). It is reasonably well documented, and we think more people will benefit from using it, of course. Schema changes tend to always remain a daunting task when you have large databases to manage.

To compare between Total Order Isolation (TOI), the default, with NBO that is available in Galera Cluster Enterprise Edition (EE), we create a test table:

CREATE TABLE large;
USE large;

CREATE TABLE test_table (
    id INT PRIMARY KEY AUTO_INCREMENT,
    data VARCHAR(255),
    num1 INT,
    num2 INT,
    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);

Then we …

Codership will be a sponsor at DOAG 2024 in Nuremberg, Germany. There will also be 2 Galera Cluster related talks to attend:

1. Building a Global, High-Availability Database with Galera Cluster: A Live Demo Colin Charles Codership
2. Safe Harbor! Wie der Galera Cluster ihre MySQL Datenbanken „unsinkbar“ macht. Matthias Jung Ordix

There are also a few Galera Cluster blog posts in German from our partner Ordix that are useful:

1. …

By now you must have read our documentation on isolation levels and also our Support for Transaction Isolation Levels. It is worth noting that the default transaction isolation level in MySQL 8 is REPEATABLE READ.

Here is a simple example of this, in action (you can test this on two different nodes, even across a 9-node Galera Cluster!).

First we do some simple setup:

CREATE DATABASE isolate;

USE isolate;

CREATE TABLE products (
id INT PRIMARY KEY,
name VARCHAR(50),
price DECIMAL(10, 2)
);

Then we insert some initial data:

INSERT INTO products (id, name, …

Well, that is more a catchy headline, than the reality: XA transactions work in your Galera Cluster Enterprise Edition (EE). This has been supported since our very first release with 8.0.28 Enterprise, right up till now, in 8.0.39 Enterprise. If you try to run an XA transaction in your regular Galera Cluster you’ll be given an error as such:

mysql> XA START 'xatest';
ERROR 1235 (42000): This version of MySQL doesn't yet support 'XA with wsrep replication plugin'

However, with Galera Cluster Enterprise Edition (EE), XA transactions, “just work”. What is an XA transaction, you might ask? An XA transaction is a distributed transaction …

Codership is pleased to announce a new beta preview release of the multi-master Galera Cluster for MySQL 8.4, consisting of MySQL-wsrep 8.4.2-26.20 (release notes, download), with Galera replication library 4.20 (release notes, download) implementing wsrep API version 26. This release incorporates all changes to MySQL 8.4.2, adding a synchronous option for your MySQL High Availability solutions.

One will notice that MySQL-wsrep 8.4.2-26.20 uses …

Codership is pleased to announce a new Generally Available (GA) release of the multi-master Galera Cluster for MySQL 8.0, consisting of MySQL-wsrep 8.0.39-26.20 (release notes, download), with Galera replication library 4.20 (release notes, download) implementing wsrep API version 26. This release incorporates all changes to MySQL 8.0.39, adding a synchronous option for your MySQL High Availability solutions.

In the Galera replication …

Codership is pleased to announce a new Generally Available (GA) release of the multi-master Galera Cluster for MySQL 8.0, consisting of MySQL-wsrep 8.0.36-26.18 (release notes, download). There is no change to the Galera replication library 4.18 (release notes, download) implementing wsrep API version 26. This release incorporates all changes to MySQL 8.0.36, adding a synchronous option for your MySQL High Availability solutions.

This is a …

Codership is pleased to announce a new Generally Available (GA) release of the multi-master Galera Cluster for MySQL 8.0, consisting of MySQL-wsrep 8.0.36 (release notes, download), with Galera replication library 4.18 (release notes, download) implementing wsrep API version 26. This release incorporates all changes to MySQL 8.0.36, adding a synchronous option for your MySQL High Availability solutions.

There have been some notable changes …