MySQL sync cluster fault tolerance

By default, a MySQL sync Managed Database cluster consists of one master node. To provide fault tolerance for the cluster, you need to add replicas to it. In multi-node clusters, one node will be the master node, and the others will be replicas.

note

For example, if you have created a three-node cluster, the cluster will have one master node and two replicas. If you add more nodes, they will be replicas.

A MySQL sync cluster with replicas has limitations.

When adding replicas, consider the node allocation type in the cluster.

Master node

By default, the cluster consists of one primary node—the master node. When connected to the master node, all operations are available: reading (SELECT) and writing (INSERT, UPDATE, DELETE, and others).

All data changes on the master node are replicated to the replicas. The replication process does not affect the performance of the replicas and the master node.

Replicas

Replicas are full copies of the master node. They are available for read-only operations (SELECT).

Having replicas in a cluster ensures its fault tolerance — if the master node stops working, its role will be transferred to one of the replicas, and the cluster will continue to operate normally. When the master node is restored, it will take on the role of a replica. Note that the address of the master node will change.

An SLA applies to a cluster with replicas SLA — we guarantee 99.95% write availability and 99.99% read availability.

If a cluster has no replicas, it will be unavailable until the master node is restored. Data will not be lost.

We recommend creating fault-tolerant clusters with replicas or adding replicas to existing clusters.

Node placement type

The node placement type in a cluster depends on:

• whether there are replicas in the cluster;
• the type of pool where the cluster is located;
• the number of segments in the pool;
• the configuration line.

You can view the list of pools and segments in the Servercore Infrastructure guide Locations: countries, regions, availability zones, pools, and data center addresses.

Four node placement types are available:

• Single-Segment;
• Multi-Segment;
• Single-AZ;
• Multi-AZ.

Single-Segment

ноды размещаются in одном сегменте однозонального пула. применимо:

• clusters without replicas;
• clusters with replicas located in pools with only one segment;
• clusters with replicas in HighFreq and Dedicated configuration lines.

note

For example, you have created a three-node cluster (one master node and two replicas) in a HighFreq configuration in the ru-2 pool. All nodes will be placed in the same pool segment, for example, in ru-2c.

Multi-Segment

ноды размещаются in разных сегментах однозонального пула. применимо для кластеров with репликами, которые находятся in пулах with несколькими сегментами.

Segments are located in different racks of the same data center. Nodes are distributed across segments sequentially.

note

For example, you have created a four-node cluster (one master node and three replicas) in the ru-1 pool. The first three nodes will be placed sequentially in pool segments ru-1a, ru-1b, and ru-1c. The fourth node will be placed in segment ru-1a. If you add a fifth node, it will be placed in pool segment ru-1b.

Single-AZ

ноды размещаются in одном сегменте мультизонального пула. применимо для кластеров без реплик in пуле ru-6.

If you add a replica to the cluster, the node placement type will change to Multi-AZ.

note

For example, you have created a single-node cluster in the ru-6 pool. The node will be placed in one pool segment, for example, in ru-6a.

Multi-AZ

ноды размещаются in разных сегментах мультизонального пула. применимо для кластеров with репликами in пуле ru-6.</g.

Each pool segment is located in a separate data center. Nodes are distributed across segments sequentially.

note

For example, you have created a four-node cluster (one master node and three replicas) in the ru-6 pool. The first three nodes will be placed sequentially in pool segments ru-6a, ru-6b, and ru-6c. The fourth node will be placed in segment ru-6a. If you add a fifth node, it will be placed in pool segment ru-6b.

Change the number of replicas

You can increase or decrease the number of replicas. When the number of replicas is changed, the cluster continues to function.

1. In the Dashboard, on the top menu, click Products and select Managed Databases.
2. Open the Active tab.
3. Open the cluster page → Settings tab.
4. Click Change configuration.
5. In the Fault Tolerance block, in the Node count field, specify the new number of replicas. If there are no free addresses in the subnet to which the cluster is connected, a replica cannot be added, as each new replica occupies a new address in the subnet.
6. Click Save.