ApsaraDB RDS:Change the specifications of an ApsaraDB RDS for MySQL instance

For more information about the specific configuration items of an RDS instance, see Configuration items for an ApsaraDB RDS for MySQL instance.

For more information about how to change the specifications of an RDS instance that runs a different database engine, see the following topics:

• Change the specifications of an ApsaraDB RDS for SQL Server instance
• Change the specifications of an ApsaraDB RDS for PostgreSQL instance
• Change the specifications of an ApsaraDB RDS for MariaDB TX instance

Prerequisites

• Your Alibaba Cloud account does not have unpaid renewal orders.
• The RDS instance is in the Running state.

Limits

• After you submit a specification change order, you cannot cancel the order. Therefore, before you submit a specification change order, we recommend that you evaluate whether the new specifications meet your business requirements.
• When you change the specifications of a read-only RDS instance, the primary RDS instance to which the read-only RDS instance is attached must be in the Running state.
• The storage capacity of a read-only RDS instance must be greater than or equal to the storage capacity of the primary RDS instance to which the read-only RDS instance is attached.
• Only the configuration items that are described in Configuration items for an ApsaraDB RDS for MySQL instance can be changed.
• If you reduce the storage capacity of your RDS instance that uses local SSDs, the new storage capacity must be greater than or equal to 120% of storage that is used. For example, if the storage capacity of your RDS instance that uses local SSDs is 100 GB and 50 GB of storage is used, the new storage capacity must be greater than or equal to 60 GB (50 × 120%).

Impacts

Billing

For more information, see Specification change fees.

Procedure

1. Access RDS Instances, select a region at the top, and then click the ID of the target RDS instance.
2. In the Configuration Information section of the Basic Information page, click Change Specifications.
3. In the dialog box that appears, select a specification change method and click Next step. This step is required only when the RDS instance uses the subscription billing method.
   Note You can select one of the following specification change methods: Upgrade or Downgrade.

   • After you change the specifications, the new specifications immediately take effect. These specification change methods are supported for both subscription RDS instances and pay-as-you-go RDS instances.
   • After you submit a specification change order, ApsaraDB RDS synchronizes the data of the RDS instance from the disk to a new RDS instance. Then, ApsaraDB RDS switches the information such as the ID and endpoints about the original RDS instance over to the new RDS instance based on the specification change method that you select. You can use the same ID and endpoints to connect to your RDS instance.
   • To upgrade the specifications, you must select Upgrade and pay for the price difference based on the new specifications.
   • To downgrade the specifications, you must select Downgrade, and the system will refund you the price difference based on the new specifications.
4. Change the specifications of the RDS instance.
   Note

   • You can change the instance type and storage capacity of the RDS instance regardless of the instance configuration. For more information, see Primary ApsaraDB RDS for MySQL instance types (x86).
   • If the RDS instance runs MySQL 5.6 on RDS Enterprise Edition, you can downgrade the RDS instance to RDS High-availability Edition.
   • If the RDS instance runs MySQL 5.7 on RDS Basic Edition, you can upgrade the RDS instance to RDS High-availability Edition with local SSDs.
   • Make sure the new specifications that you specify for the RDS instance meet your business requirements.
5. Configure the Switching Time parameter.
   • Execute Immediately: After the data of the RDS instance is migrated to a new RDS instance, ApsaraDB RDS immediately switches your workloads over to the new RDS instance.
   • Switch Within Maintenance Window: ApsaraDB RDS switches your workloads over to the new RDS instance within the maintenance window that you specify. For more information, see Set the maintenance window of an ApsaraDB RDS for MySQL instance.

   Note

   • If you are using RDS Basic Edition, no secondary RDS instance is provided as a hot standby for the RDS instance. Therefore, your database service is unavailable during a specification change for a long period of time. We recommend that you change the specifications of the RDS instance during off-peak hours to prevent interruptions to your workloads.
   • If you are not using RDS Basic Edition, one or two transient connections that each lasts approximately 30 seconds may occur during the specification change. The transient connections do not interrupt your workloads. However, we still recommend that you change the specifications of the RDS instance during off-peak hours or make sure that your application is configured to automatically reconnect to the RDS instance.
   • If you select Switch Within Maintenance Window, the RDS instance stays in the upgrading or downgrading state until the switchover is complete. During the switchover process, you cannot perform specific operations on the RDS instance. For example, you cannot upgrade or downgrade the RDS instance, upgrade the database engine version of the RDS instance, or migrate the RDS instance across zones.
   • In most cases, the storage capacity expansion or change in the ESSD storage type does not interrupt your workloads and can immediately take effect. In this case, you do not need to select Switch Within Maintenance Window.
6. Read and select Terms of Service and click Pay Now. In the dialog box that appears, confirm the instance information before and after the specification change and click Continue to complete the payment.
   Warning

   • After you submit a specification change order, you cannot cancel the order. Before you submit a specification change order, we recommend that you evaluate whether the new specifications meet your business requirements.
   • After you submit a specification change order, do not perform DDL operations before the specification change is applied.

FAQ

• 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 Migrate an ApsaraDB RDS for MySQL instance across zones in the same region. 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 ApsaraDB RDS migrate the data of my RDS instance to a new RDS instance?

  In most cases, if your RDS instance uses standard SSDs or ESSDs and does not run RDS Basic Edition, no transient connections occur when you expand the storage capacity. If your RDS instance uses local SSDs, ApsaraDB RDS 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, ApsaraDB RDS creates a primary RDS instance and a secondary RDS instance on a different host that can provide sufficient storage. Then, ApsaraDB RDS 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 ApsaraDB RDS automatically upgrade the read-only RDS instances that are attached to my primary RDS instance?

  No, when you upgrade your primary RDS instance, ApsaraDB RDS 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?

Related operations