Deploy Galera Cluster Topology with Enterprise Server 10.5
This procedure describes the deployment of the Galera Cluster topology with MariaDB Enterprise Server 10.5 and MariaDB MaxScale 2.5.
MariaDB Enterprise Cluster is powered by Galera.
MariaDB Enterprise Cluster provides read scalability and fault tolerance through virtually synchronous multi-primary certification-based write-set replication (wsrep).
This procedure has 6 steps, which are executed in sequence.
MariaDB products can be deployed in many different topologies to suit specific use cases. Enterprise Cluster can be deployed on its own, or integrated with MariaDB Replication to integrate with other clusters or topologies.
This procedure represents basic product capability with 3 Enterprise Cluster nodes and 1 MaxScale node.
This page provides an overview of the topology, requirements, and deployment procedures.
Please read and understand this procedure before executing.
Customers can obtain support by submitting a support case.
The following components are deployed during this procedure:
Modern SQL RDBMS with high availability, pluggable storage engines, hot online backups, and audit logging.
Database proxy that extends the availability, scalability, and security of MariaDB Enterprise Servers
MariaDB Enterprise Server Components
MariaDB MaxScale Components
Tracks changes in the state of MariaDB Enterprise Servers operating as Enterprise Cluster nodes
Listens for client connections to MaxScale, then passes them to the router service associated with the listener
Read Connection Router
Routes connections from the listener to any available Enterprise Cluster node
Read/Write Split Router
Routes read operations from the listener to any available Enterprise Cluster node, and routes write operations from the listener to a specific server that MaxScale uses as the primary server
Connection configuration in MaxScale to an Enterprise Cluster node
MariaDB Enterprise Cluster topology provides read scalability through certification-based write-set replication (wsrep) that is multi-primary and virtually synchronous.
The Enterprise Cluster topology consists of:
1 or more MaxScale nodes
3 or more MariaDB Enterprise Servers (ES) configured as Enterprise Cluster nodes
The MaxScale nodes:
Monitor the health and availability of each Enterprise Cluster node using the Galera Monitor (
Accept client and application connections
Route queries to the Enterprise Cluster nodes using the Read Connection (
readconnroute) or the Read/Write Split (
The Enterprise Cluster nodes:
Receive queries from MaxScale
Store data locally using the InnoDB storage engine
Perform certification-based virtually synchronous replication to other Enterprise Cluster nodes
Provide State Snapshot Transfers (SST) to bring MariaDB Enterprise Server nodes into sync with the cluster
These requirements are for the Galera Cluster topology when deployed with MariaDB Enterprise Server 10.5 and MariaDB MaxScale 2.5.
MaxScale nodes, 1 or more are required.
Enterprise Cluster nodes, 3 or more are required.
To avoid problems in establishing a quorum in the event of a network partition or outage, MariaDB recommends deploying an odd number of Enterprise Cluster nodes. When using multiple network switches, deploy across an odd number of switches, each with an odd number of nodes. When using multiple data centers, deploy across an odd number of data centers, each with an odd number of switches.
In alignment to the enterprise lifecycle, the Galera Cluster topology with MariaDB Enterprise Server 10.5 and MariaDB MaxScale 2.5 is provided for:
CentOS Linux 7 (x86_
CentOS Linux 8 (x86_
Debian 9 (x86_
Debian 10 (x86_
Debian 11 (x86_
Red Hat Enterprise Linux 7 (x86_
Red Hat Enterprise Linux 8 (x86_
Red Hat Enterprise Linux 9 (x86_
Rocky Linux 8 (x86_
Rocky Linux 9 (x86_
SUSE Linux Enterprise Server 12 (x86_
SUSE Linux Enterprise Server 15 (x86_
Ubuntu 18.04 LTS (x86_
Ubuntu 20.04 LTS (x86_
Ubuntu 22.04 LTS (x86_
MariaDB Enterprise Server Configuration Management
MariaDB Enterprise Server packages are configured to read configuration files from different paths, depending on the operating system. Making custom changes to Enterprise Server default configuration files is not recommended because custom changes may be overwritten by other default configuration files that are loaded later.
To ensure that your custom changes will be read last, create a custom configuration file with the
z- prefix in one of the include directories.
Example Configuration File Path
MariaDB Enterprise Server Service Management
systemctl command is used to start and stop the MariaDB Enterprise Server service. The
galera_recovery scripts are used for Enterprise Cluster-specific operations.
Enable during startup
Disable during startup
Bootstrap a cluster node
Recover a cluster node's position
MariaDB Enterprise Server Logs
MariaDB Enterprise Server produces log data that can be helpful in problem diagnosis.
Log filenames and locations may be overridden in the server configuration. The default location of logs is the data directory. The data directory is specified by the datadir system variable.
MariaDB Enterprise Audit Log
Slow Query Log
General Query Log
MaxScale Configuration Management
MaxScale can be configured using several methods. These methods make use of MaxScale's REST API.
Command-line utility to perform administrative tasks through the REST API. See MaxCtrl Commands.
MaxGUI is a graphical utility that can perform administrative tasks through the REST API.
The REST API can be used directly. For example, the
The procedure on these pages configures MaxScale using MaxCtrl.
MaxScale Service Management
systemctl command is used to start and stop the MaxScale service.
Enable during startup
Disable during startup