Disk autoscaling
VK Cloud supports automatic scaling of database disks. When the amount of free disk space reaches a threshold value, the disk size is automatically increased by the expansion step. This increase is limited by the specified maximum disk size.
Autoscaling is supported for the following types of disks:
- Data disk — a disk with data connected to the VM in addition to the main disk.
- WAL disk — a disk storing the write-ahead log (Write-Ahead Log, WAL). Only for PostgreSQL databases in Single, Master-Replica, and Cluster configurations.
Parameter | Data disk | WAL disk |
|---|---|---|
Maximum disk size, GB | Set manually and cannot exceed:
| Calculated automatically and cannot be set by the user |
Threshold value, GB | Calculated by the formula: If the value obtained by the formula is greater than | Calculated by the formula: If the value obtained by the formula is greater than |
Expansion step, GB | Calculated by the formula: If the value obtained by the formula is greater than | Calculated by the formula: If the value obtained by the formula is greater than |
-
The user enables autoscaling and sets the maximum disk size: when creating an instance or after its deployment.
-
The free disk space reaches the threshold value at which autoscaling should trigger.
-
The service calculates the expansion step and determines whether the disk can be scaled:
- If the new disk size (current size + expansion step) does not exceed the specified maximum size, the disk size is increased.
- If the new disk size exceeds the specified maximum size, autoscaling is not performed.
The table below shows for which configurations and DBMS versions disk autoscaling is supported.
DBMS type | Single | Master-Replica | Cluster |
|---|---|---|---|
MySQL (all versions) | |||
PostgreSQL (all versions) | |||
ClickHouse (all versions) | |||
Redis 5 | |||
Redis 6 | |||
MongoDB 4.0 | |||
OpenSearch 2 |