This topic describes how to change the specifications of an ApsaraDB RDS for MySQL instance. The specifications include the RDS edition, instance type, and storage capacity.

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

Prerequisites

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

Precautions

  • In the RDS Basic Edition, your RDS instance does not have a secondary RDS instance as a hot standby. If your RDS instance unexpectedly fails, your database service becomes unavailable. If you change the specifications or upgrade the database engine version of your RDS instance, your database service also becomes unavailable. The unavailability may last for a long period of time. If your workloads require high service availability, we recommend that you do not select the RDS Basic Edition.
  • If you change the specifications of your RDS instance, a data migration may be triggered. After the data migration is completed, ApsaraDB RDS switches over your workloads during the specified switching time. The switchover does not interrupt the synchronization of incremental data. However, the switchover causes a transient connection error of about 30 seconds. During the switchover, 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 during off-peak hours. Otherwise, make sure that your application is configured to automatically reconnect to your RDS instance.
    Note In most cases, if your RDS instance uses standard or enhanced SSDs and does not run the RDS Basic Edition, no transient connection errors occur when you increase the storage capacity.
  • You can create read-only RDS instances to increase the read capability of your database system. The read-only RDS instances offload read requests from your RDS instance. For more information, see Create a read-only ApsaraDB RDS for MySQL instance.
  • After you change the specifications of your RDS instance, you do not need to manually restart the instance.
  • After you change the specifications of your RDS instance, the ID and endpoints of your RDS instance remain unchanged.

Billing

For more information, see Specification change fees.

Procedure

  1. Go to the Basic Information page.
    1. Log on to the ApsaraDB for RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your RDS instance resides.
      选择地域
    2. Find your RDS instance and click its ID. In the left-side navigation pane, click Databases.
    3. In the left-side navigation pane, click Basic Information.
  2. In the Configuration Information section of the Basic Information page, click Change Specifications.
  3. In the dialog box that appears, select a change method and click Next. This step is required only when your RDS instance uses the subscription billing method.
    Note You can select the Upgrade or Downgrade option for both subscription and pay-as-you-go RDS instances. The new specifications immediately take effect.
  4. Change the specifications of your RDS instance.
    Note
    • You can change the specifications and storage capacity of your RDS instance regardless of the instance configuration.
    • If your RDS instance runs MySQL 5.6, you can change the RDS edition from Enterprise to High-availability.
  5. Set the Switching Time parameter.
    • Switch Immediately After Data Migration: ApsaraDB RDS immediately switches over your workloads after the data migration is completed.
    • Switch Within Maintenance Window: ApsaraDB RDS switches over your workloads within the specified maintenance window. For more information, see Set the maintenance window of an ApsaraDB RDS for MySQL instance.
    Warning
    • In the RDS Basic Edition, your RDS instance does not have a secondary RDS instance as a hot standby. When you change the specifications of your RDS instance, your database service may be unavailable for a long period of time. We recommend that you change the specifications of your RDS instance during off-peak hours to prevent interruptions to your workloads.
    • When the specification change is being applied, a transient connection error of about 30 seconds may occur. In this case, you cannot perform most of the operations that are related to databases, accounts, and network settings. This applies if your RDS instance does not run the RDS Basic Edition. We recommend that you change the specifications of your RDS instance during off-peak hours to prevent interruptions to your workloads.
  6. Read and select Terms of Service, click Pay Now, and then complete the payment.

FAQ

  • How do I switch my RDS instance among the local, standard, and enhanced SSD storage types?

    For more information, see How to change a cloud disk to a local disk.

  • When I expand the storage capacity of my RDS instance, an error that indicates insufficient storage resources is returned. What do I do?

    Migrate your RDS instance to another zone and try 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 another zone, the endpoints of your RDS instance remain unchanged. However, the IP addresses that are bound to the endpoints of your RDS instance may change. We recommend that you configure your application to automatically reconnect to your RDS instance.

  • If I only expand the storage capacity of my RDS instance, do I need to migrate data to a new RDS instance?

    In most cases, if your RDS instance uses standard or enhanced SSDs and does not run the RDS Basic Edition, no transient connection errors occur when you expand the storage capacity. If your RDS instance uses local SSDs, you may encounter the following circumstances:

    • The host on which your RDS instance runs can provide sufficient storage resources. In this case, you can directly expand the storage capacity. The expansion does not interrupt your workloads.
    • The host on which your RDS instance runs cannot provide sufficient storage resources. In this case, ApsaraDB RDS creates new primary and secondary RDS instances on another qualified host. 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 completed, a transient connection error of about 30 seconds occurs.
    Note You cannot query the remaining storage space of the host on which an RDS instance runs.
  • When I upgrade my primary RDS instance, does ApsaraDB RDS upgrade the read-only RDS instances?

    No, when you upgrade your primary RDS instance, ApsaraDB RDS does not upgrade the read-only RDS instances. 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 Precautions.

  • After I change the specifications of my RDS instance, do the endpoints of the instance change?

    No, after you change the specifications of your RDS instance, the endpoints of the instance remain unchanged. An example endpoint is rm-bpxxxxx.mysql.rds.aliyuncs.com. However, the IP addresses that are bound to the endpoints may change. We recommend that you add the endpoints to your application. Do not add the IP addresses to your application.

Related operations

Operation Description
ModifyDBInstanceSpec Changes the specifications of an ApsaraDB RDS instance.