MySQL sync cluster fault tolerance

Last update: October 05 2026Open in Markdown

By default, a MySQL sync Managed Databases cluster consists of a single master node. To ensure cluster fault tolerance, you need to add replicas to it. In multi-node clusters, one node will be the master node, and the rest 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: a master node. When connecting to the master node, all operations are available: read (SELECT) and write (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 exact copies of the master node. They are only available for reading data (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 — 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;
• configuration lines.

You can view the list of pools and segments in the Selectel infrastructure table in the Locations: countries, regions, availability zones, pools, and data center addresses manual.

There are four available node placement types:

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

Single-Segment

Nodes are placed in a single segment of a single-zone pool. Applicable to:

• for clusters without replicas;
• clusters with replicas located in pools with only one segment;
• clusters with replicas in configurations of the HighFreq and Dedicated lines.

note

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

Multi-Segment

Nodes are placed in different segments of a single-zone pool. Applicable to clusters with replicas located in pools with multiple segments.

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 the pool segments ru-1a, ru-1b, and ru-1c. The fourth node will be placed in the ru-1a segment. If you add a fifth node, it will be placed in the ru-1b pool segment.

Single-AZ

Nodes are placed in a single segment of a multizone pool. Applicable to:

• for clusters without replicas in the ru-6 and uz-1 pools;
• clusters with replicas in the uz-1 pool in configurations of the HighFreq line.

note

For example, you created a three-node cluster (one master node and two replicas) in a HighFreq line configuration in the uz-1 pool. All nodes will be placed in a single pool segment, for example in uz-1b.

Multi-AZ

Nodes are placed in different segments of a multizone pool. Applicable to:

• for clusters with replicas in the ru-6 pool;
• clusters with replicas in the uz-1 pool, except for configurations of the HighFreq line.

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

note

For example, you 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 the ru-6a, ru-6b, and ru-6c pool segments. The fourth node will be placed in the ru-6a segment. If you add a fifth node, it will be placed in the ru-6b pool segment.

Change the number of replicas

You can increase or decrease the number of replicas. When changing the number of replicas, the cluster continues to work.

1. In the control panel, in the top menu, click Products and select Cloud Databases.
2. Open the Active tab.
3. Open the cluster page → Settings tab.
4. Click Edit configuration.
5. In the Fault tolerance block, in the Number of nodes field, specify the new number of replicas. If there are no available addresses in the subnet to which the cluster is connected, the replica cannot be added — each new replica takes a new address in the subnet.
6. Click Save.