{"id":43935,"date":"2024-06-14T10:34:24","date_gmt":"2024-06-14T10:34:24","guid":{"rendered":"https:\/\/accuweb.cloud\/resource\/?post_type=faq&p=43935"},"modified":"2025-01-17T10:52:45","modified_gmt":"2025-01-17T10:52:45","slug":"mariadb-multi-region-cluster","status":"publish","type":"faq","link":"https:\/\/accuweb.cloud\/resource\/articles\/mariadb-multi-region-cluster","title":{"rendered":"MariaDB Multi-Region Cluster"},"content":{"rendered":"

MariaDB Multi-Region Cluster<\/h1>\n

MariaDB Multi-Region Cluster is a sophisticated, highly available solution that automatically sets up an advanced cluster using platform-managed stack templates.<\/p>\n

Database Cluster Topology<\/h2>\n

The MariaDB Multi-Region clustering<\/a> utilizes a Primary-Primary topology, featuring asynchronous replication to mitigate the latency effects on transaction commits. This approach is particularly advantageous when dealing with regions (data centers) that are geographically distant from one another.<\/p>\n

For disaster recovery purposes, one or more Secondary nodes can be incorporated to ensure robust cross-region deployment. On platforms offering three regions, the recommended configuration is Primary-Primary-Secondary.<\/strong><\/p>\n

\"cross-region<\/a>
\nEvery database server or load balancer<\/a> node within the cluster topology is established in a distinct environment.<\/p>\n

A ProxySQL Load Balancer layer is positioned in front of the cluster to distribute requests between the Primary nodes. Once created, these environments are unified into a multi-region cluster.<\/p>\n

This package delivers out-of-the-box high availability and failover for the database cluster. High availability is guaranteed at the data center level, ensuring the database remains accessible even if one of the regions goes down.<\/p>\n

If a Primary region fails, the cluster continues to handle both Read and Write queries. Should both Primary regions become unavailable, the Secondary node can still manage Read and Write requests without data loss.<\/p>\n

However, this will necessitate updating the entry point setting in the database client application to replace the ProxySQL hostnames with the hostname of the Secondary database server.<\/p>\n

\t\t
\n\t\t\t
\n \n
\n
\n
\n \n \t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t<\/div>\n
<\/div>\n

Cluster Installation<\/h2>\n

1. Locate the Application<\/h3>\n

Navigate to the platform Marketplace<\/a> and find the MariaDB Multi-Region Cluster application within the Clusters section or by using the Search field.<\/p>\n

\"Locate<\/a><\/p>\n

2. Configuration<\/h3>\n

In the installation window, specify the following details:
\nRegions<\/strong>: Choose the specific platform regions where your cluster environments will be deployed.
\nThe order of regions is crucial, as the first two will host the Primary servers, and any additional regions will host the Secondary servers.<\/p>\n

Stack<\/strong>: Choose the preferred stack for your cluster:<\/p>\n