Automatic space expansion increases your database instance's storage when it runs low. You define a threshold, and when the available storage drops to that level, the system automatically expands the storage. This helps prevent data loss and business disruptions from database crashes. The instance is not restarted during the expansion, so your services are not affected.
Prerequisites
-
The database instance must be a supported type and located in a supported region.
Database
Region
-
ApsaraDB RDS for MySQL Basic, High-availability, or Cluster Edition (with cloud disks)
-
PolarDB for MySQL Standard Edition
This feature relies on anomaly detection and is available only in regions that support it. The following regions are supported:
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Nanjing - Local Region - Phasing Out), China (Fuzhou - Local Region - Phasing Out), China (Chengdu), China (Zhengzhou), China (Hong Kong), Japan (Tokyo), South Korea (Seoul), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), Thailand (Bangkok), UAE (Dubai), Saudi Arabia (Riyadh), Germany (Frankfurt), US (Silicon Valley), US (Virginia), and UK (London)
ApsaraDB RDS for SQL Server High-availability or Cluster Edition (with cloud disks)
NoteApsaraDB RDS for SQL Server read-only instances do not support enabling automatic space expansion independently.
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Chengdu), China (Hong Kong), Japan (Tokyo), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), UAE (Dubai), Germany (Frankfurt), US (Silicon Valley), US (Virginia), and UK (London)
-
-
Ensure that your account has a sufficient balance to pay for the expansion.
-
A service-linked role for DAS is created.
NoteIf you have not created a service-linked role for DAS, the system automatically creates one before the first automatic space expansion.
Background information
For more information, see DAS Auto Scaling capabilities.
Usage notes
-
When automatic space expansion is triggered for a primary instance with read-only instances, the system first expands any read-only instance whose storage is smaller than the primary instance's target size. Only after expanding all required read-only instances does the system expand the primary instance.
-
Due to Windows driver limitations, this feature is unavailable for some instances. We recommend that you upgrade the minor engine version of SQL Server.
Billing
The billing rules are the same as those for manually upgrading the storage space of an RDS instance. For more information, see Billing rules for configuration changes.
Procedure
Log on to the DAS console.
In the navigation pane on the left, click .
Find the target instance and click the instance ID to open the instance details page.
-
In the navigation pane on the left, click Autonomy Center.
-
On the Autonomy Center page, click Autonomy Service Settings on the right.
-
On the tab, enable the autonomy service.
-
On the Optimization and Throttling tab, select the Automatic Space Expansion checkbox and configure the following parameters.
Parameter
Description
Available Storage Space ≤
The expansion threshold.
When the available storage space of your instance is less than or equal to this threshold, the system expands the storage by the larger of the following two values:
-
5 GB
NoteIf the total storage space of the instance is less than 50 GB and the available storage space is less than 10% of the total storage, the expansion step is adjusted to 10 GB.
-
15% of the current total storage of the instance (rounded to the nearest multiple of 5).
For example, if your total storage is 100 GB, the expansion increment is 15 GB (15% of 100 GB, which is greater than the 5 GB minimum). After a successful expansion, the total storage will be 115 GB.
NoteFor PolarDB for MySQL Standard Edition database instances, the expansion threshold is set by the system and does not require manual configuration. For details about the thresholds, see Scale-out thresholds for PolarDB for MySQL Standard Edition.
Maximum Storage of Automatic Expansion
The maximum total storage space the instance can reach through automatic expansion. This value must be greater than or equal to the instance's current total storage.
ImportantFor PolarDB for MySQL Standard Edition database instances, the expansion step size is a multiple of 10. We recommend that you set Maximum Storage of Automatic Expansion to a multiple of 10. Otherwise, the expansion may fail or may not reach the specified Maximum Storage of Automatic Expansion.
NoteThe minimum interval between successive expansion operations is 10 minutes.
-
-
Click OK.
-
Configure an Alert Template to receive notifications about automatic space expansions.
The system recommends an alert template with the appropriate alert rules. Follow the prompts to complete the configuration.
Note-
If you have already configured an alert template for the instance, follow the prompts to add alert rules for the corresponding autonomous events to the template.
-
If you need to configure the alert template and rules yourself, see Configure alert templates and Configure alert rules.
-
-
Select a Alert Contact Group to receive alert notifications.
-
Click Add Contact to add a new alert contact.
-
Click Create Contact Group to add a new contact group.
-
Click Modify or Remove next to a contact to modify or delete their information.
For more information, see Manage alert contacts.
-
-
Click Submit Configuration and confirm the settings in the subsequent dialog box.
View automatic expansion results
Log on to the DAS console.
In the navigation pane on the left, click .
Find the target instance and click the instance ID to open the instance details page.
-
In the navigation pane on the left, click Autonomy Center.
-
On the Autonomy Center page, view the Auto-Scaling Events for the selected time range.
-
Click Details to view the details of the automatic space expansion. In the event list, a record named Auto-scaling event with an event level of Notice is displayed. Click the Details button on its right.
PolarDB for MySQL Standard Edition scale-out thresholds
The expansion threshold depends on the instance's total storage space, as shown in the table below:
|
Total storage space |
Expansion threshold |
|
Less than 120 GB |
Available storage space < 50% of total storage space |
|
120 GB to less than 1 TB |
Available storage space < 30% of total storage space |
|
1 TB to less than 10 TB |
Available storage space < 20% of total storage space |
|
10 TB or more |
Available storage space < 10% of total storage space |
Related documents
-
After an automatic space expansion, automatic space shrinking is not currently supported. To shrink the space, you must manually change the configuration. For more information, see Change configuration.
NoteManual scale-in is not supported for ApsaraDB RDS for SQL Server or PolarDB for MySQL Standard Edition instances.
-
You can enable automatic fragment reclamation to clean up table space fragments and reduce wasted storage space.
-
You can use the storage analysis and capacity assessment features to analyze your storage usage.
-
If your database instance is ApsaraDB RDS for PostgreSQL, see Automatic storage expansion.
-
If your database instance is PolarDB for MySQL, see Set automatic expansion for ESSD cloud disks.