Skip to main content

Volumes in MySQL semi-sync cluster

In a Managed Database cluster MySQL semi-sync, you can use local and network disks. The disk type used depends on the selected configuration line.

You can select a configuration line with the desired disk type and disk size when creating a Managed Database cluster. After creating the cluster, you can change the line to another one with the same disk type and increase the disk size — scale the cluster.

You can check disk performance and throughput in different configuration lines in the Performance and throughput table.

Local disks

Configuration lines
  • Standard;
  • CPU;
  • Memory;
  • HighFreq;
  • Dedicated;
  • Flex
Disk typeSSD NVMe disk
Technical specifications The disk subsystem is configured in RAID 1 for the Dedicated lineup and in RAID 10 for the Standard, CPU, Memory, HighFreq, and Flex lineups
AdvantagesLow data access latency
UsageSuitable for tasks sensitive to read and write performance
Number of disks in the DBMS1
Changing configuration
  • in all configuration lines with a local disk, except Flex, you cannot increase only the local disk, you can change the entire node configuration — scale the cluster;
  • you can change a configuration line with a local disk to a line with a network disk only when restoring the cluster
Detaching a disk✗
Connecting to another database✗
Creating another disk, snapshot, or backup✗
DeletionDeleted along with all data when the cluster is deleted

Network volumes

Configuration linesFlex
Disk typeSSD NVMe disk
Technical specificationsManaged by a software-defined storage (SDS) system — Ceph
Advantages
  • triple disk volume replication;
  • network volume size is independent of the number of vCPUs
UsageNot recommended for systems sensitive to network latency and response time. For example, suitable for data archiving
Number of disks in the DBMS1
Changing configuration
  • no downtime when changing disk size;
  • when changing the number of vCPUs and RAM, downtime depends on the number of nodes in the cluster: in single-node clusters, downtime is equal to the node reboot time (one to two minutes), and in multi-node clusters — the time taken to switch to another node (less than one minute);
  • you can change a configuration line with a network disk to a line with a local disk only when restoring the cluster
Detaching a disk✗
Connecting to another database✗
Creating another disk, snapshot, or backup✗
DeletionDeleted along with all data when the cluster is deleted

Performance and throughput

Volumes
up to 256 GB		Volumes
512 GB		Volumes
768 GB		Volumes
1 TB		Volumes
1.5 TB		Volumes
2 TB
Throughput400 MB/s500 MB/s600 MB/s700 MB/s800 MB/s900 MB/s
Performance (read)25600 IOPS40000 IOPS50000 IOPS60000 IOPS70000 IOPS80000 IOPS
Performance (write)12800 IOPS20000 IOPS25000 IOPS30000 IOPS35000 IOPS40000 IOPS