How do I change the storage type of my RDS instance between local SSDs, standard SSDs, and ESSDs?
For more information, see How do I change the storage type of an ApsaraDB RDS instance from standard SSD or ESSD to local SSD?
When I expand the storage capacity of my RDS instance, what do I do if an error that indicates insufficient storage resources occurs?
You can migrate your RDS instance to a different zone and then expand the storage capacity of your RDS instance again. For more information, see Perform cross-zone migration. After you migrate your RDS instance to a different zone, the endpoints of your RDS instance remain unchanged. However, the IP addresses that are associated with the endpoints change. Make sure that your application is configured to automatically reconnect to your RDS instance.
If I expand only the storage capacity of my RDS instance, does the system migrate the data of my RDS instance to a new RDS instance?
In most cases, if your RDS instance uses cloud disks and does not run RDS Basic Edition, no transient connections occur when you expand the storage capacity. If your RDS instance uses local disks, the system migrates the data of your RDS instance based on the storage resources on the host on which your RDS instance is deployed:
The host on which your RDS instance is deployed can provide sufficient storage. In this case, you can directly expand the storage capacity. The expansion process does not interrupt your workloads.
The host on which your RDS instance is deployed cannot provide sufficient storage. In this case, the system creates a primary RDS instance and a secondary RDS instance on a different host that can provide sufficient storage. Then, the system synchronizes the data of your original RDS instance to the new primary and secondary RDS instances. The synchronization does not interrupt the workloads on your original RDS instance. However, after the synchronization is complete, a switchover of your workloads causes a transient connection that lasts approximately 30 seconds.
Note
You cannot obtain the amount of available storage in the host on which an RDS instance is deployed.
When I upgrade my primary RDS instance, does the system automatically upgrade the read-only RDS instances that are attached to my primary RDS instance?
No, when you upgrade your primary RDS instance, the system does not automatically upgrade the read-only RDS instances that are attached to your primary RDS instance. You must manually upgrade the read-only RDS instances.
When I change the specifications of my RDS instance, are my online workloads interrupted?
For more information, see Impacts.
After I change the specifications of my RDS instance, do the endpoints of my RDS instance change?
No, after you change the specifications of your RDS instance, the endpoints of your RDS instance remain unchanged. An example endpoint is rm-bpxxxxx.mysql.rds.aliyuncs.com. However, the IP addresses that are associated with the endpoints may change. We recommend that you add the endpoints to your application. Do not add the IP addresses to your application.
What factors affect the period of time that is required to change the specifications of my RDS instance?
For more information, see Which factors affect the time that is required to change the specifications of my ApsaraDB RDS for MySQL instance?
If I upgrade the CPU cores, memory, and storage capacity of my RDS instance at the same time, how long is the service downtime?
The service downtime lasts the same as the downtime when you upgrade the CPU cores, memory, or storage capacity of your RDS instance. In most cases, the service downtime lasts minutes. During the changes of instance specifications, an instance switchover may occur, or your RDS instance may be restarted. In addition, you cannot perform most of the operations that are related to databases, accounts, and network settings. We recommend that you change the specifications of your RDS instance within the specified maintenance window. For more information about the impacts of different configuration items, see Impacts.
When I expand the storage capacity of my RDS instance, why does a transient connection occur?
When you expand the storage capacity of your RDS instance, an instance switchover occurs. For more information about the impacts of an instance switchover, see Impacts of an instance switchover.
When I expand the storage capacity of my primary RDS instance, is data replication from the primary RDS instance to its read-only RDS instances affected?
No, specification changes do not affect data replication from the primary RDS instance to its read-only RDS instances.
Automatic storage expansion is not supported for RDS instances that use local disks. What do I do if I want to enable the automatic storage expansion feature for an RDS instance that uses local disks?
You must create an RDS instance that uses cloud disks and then migrate your data from the original RDS instance to the new RDS instance. For more information, see Migrate data between ApsaraDB RDS for MySQL instances.
How do I expand the storage capacity of my RDS instance after the upper limit is reached?
If your RDS instance uses local disks, you can expand the storage capacity of the instance by upgrading the storage type of the RDS instance to cloud disks. For more information about how to change the storage type, see Change the storage type from local SSD to ESSD or general ESSD. For more information about the storage capacity of RDS instance that runs MySQL 8.0 or MySQL 5.7 on RDS High-availability Edition and uses local disks, see RDS instances on RDS High-availability Edition (with local disks).
If I delete a database from an RDS instance, is the disk space released?
If you execute the DROP statement to delete a database, the disk space is released. If you execute the DELETE statement to delete a database, the disk space is not released and disk fragments are generated.
Can I convert a regular ApsaraDB RDS for MySQL instance into a serverless ApsaraDB RDS for MySQL instance?
No, you cannot convert a regular RDS instance into a serverless RDS instance. If you want to use a serverless RDS instance, you must create a serverless RDS instance. For more information, see Create a serverless ApsaraDB RDS for MySQL instance.
How am I charged for automatic storage expansion?
By default, the automatic storage expansion feature is disabled. In this case, you are not charged for the feature. If you enable the feature, you are charged for the feature based on the billing method that is used for manual storage expansion. For more information, see Change instance specifications.
What are the rules for automatic storage expansion?
For more information about the rules for automatic storage expansion, see Configure automatic storage expansion.
How do I change single-zone deployment to multi-zone deployment?
If you want to change single-zone deployment to multi-zone deployment, you must migrate your RDS instance across zones in the same region. For more information, see Perform cross-zone migration.
How do I configure an application to automatically reconnect to an RDS instance?
If the client uses a Java application, we recommend that you set the time to live (TTL) in the Java application to no more than 60 seconds. This way, when the virtual IP address (VIP) of the endpoint changes, the application queries the DNS records to receive and use the new VIP of the resource. For more information about how to configure the TTL, see official JDK documentation.
What should I pay attention to when I reduce the storage capacity of an RDS instance that uses cloud disks?
When you reduce the storage capacity of an RDS instance, the instance may be transiently disconnected. For more information, see How do I reduce the storage capacity of an ApsaraDB RDS for MySQL instance that uses cloud disks?