Multi-Region Cluster
MariaDB Multi-Region Cluster
MariaDB Multi-Region Cluster is a pre-packaged solution that automatically creates an advanced, highly available database cluster across multiple platform regions using platform-managed stack templates.
Database Cluster Topology
The MariaDB multi-region solution is based on a Primary-Primary topology with asynchronous replication. This design reduces the effect of inter-region latency on transaction commits and is intended for deployments where data centers are significantly separated geographically.
One or more Secondary nodes can be added for cross-region disaster recovery. On a platform with three regions, the documented recommended topology is:
Every database server or load-balancer node in the cluster topology is created in a separate environment. A ProxySQL load-balancer layer is placed in front of the database cluster to distribute requests between Primary servers. The separate environments are then combined into the multi-region cluster.
High Availability and Failover
The package provides out-of-the-box high availability and failover at the data-center level.
Secondary failover entry point
Using the Secondary database when both Primary regions are down requires an update to the application database connection setting. The Secondary node hostname or IP address becomes the temporary entry point.
Cluster Installation
Find the package in Marketplace
Open the platform Marketplace and locate MariaDB Multi-Region Cluster in the Clusters section or through the Search field.
Configure the installation
In the installation window, specify the required cluster settings:
- Regions: choose the platform regions where the cluster environments should be deployed. Region order is important: the first two regions receive Primary servers and the remaining regions receive Secondary servers.
- Database version: select the required MariaDB version.
- Environment: provide a name used to isolate and group the cluster environments.
- Display Name: provide a custom display name for the cluster environments.
Click Install when the configuration is ready.
Region order matters
The first two selected regions become the Primary database regions. Any additional selected regions are deployed as Secondary database regions.
Wait for installation
The installation can take several minutes. When it completes, the platform shows a success window and sends emails containing the cluster entry-point details and access credentials.
To view all cluster-related environments together, switch to the environment group specified during installation.
Cluster Entry Points and Access
The multi-region cluster entry point contains two items, one for each Primary server. Each link includes the cluster name and its ProxySQL hostname.
If both Primary regions become unavailable, use the hostname or IP address of the Secondary database node as the application database entry point.
Expected Result
A MariaDB database cluster is deployed across multiple platform regions with two Primary servers using asynchronous replication, optional Secondary servers for disaster recovery, and ProxySQL layers that distribute application requests between the Primary regions.
Important Notes
- The multi-region solution is based on Primary-Primary asynchronous replication.
- The first two regions selected during installation become Primary regions.
- Additional regions become Secondary database regions.
- Each database server and load-balancer node is deployed in a separate environment.
- ProxySQL is placed in front of the Primary database servers to distribute requests.
- The cluster entry point contains one ProxySQL-based item for each Primary region.
- If both Primary regions fail, the application connection setting must be changed to the Secondary database hostname or IP.