All Products
Search
Document Center

ApsaraDB RDS:Configure a serverless ApsaraDB RDS for MySQL instance

Last Updated:Jan 11, 2024

This topic describes how to modify the configuration of a serverless ApsaraDB RDS for MySQL instance if the serverless RDS instance cannot meet your business requirements. You can upgrade the RDS edition, adjust the scaling range of RDS Capacity Units (RCUs), modify the scaling policy, configure automatic start and stop, and manually start a serverless RDS instance.

Usage notes

The operations in this topic apply only to serverless RDS instances. Make sure that the billing method of your RDS instance is serverless.

Configuration items

Item

Description

Upgrade from RDS Basic Edition to RDS High-availability Edition

If a serverless RDS instance runs RDS Basic Edition, you can upgrade the RDS edition to RDS High-availability Edition. You are not charged for the upgrade operation. After the upgrade, you are charged based on the pricing for RDS High-availability Edition.

RCUs

The range of RCUs for a serverless RDS instance. The serverless RDS instance automatically adjusts the number of RCUs within the range based on your workloads.

Scaling policy

The scaling policy for a serverless RDS instance. In most cases, the RCU scaling for the serverless RDS instance immediately takes effect and does not affect your workloads. In some special cases, an instance switchover may occur. You can specify whether to forcefully scale the RCUs in the special cases. For more information about the impacts of an instance switchover, see Impacts of an instance switchover.

Note

Instance switchovers are countermeasures in emergency cases. The probability of instance switchovers is extremely low.

Automatic start and stop

Specifies whether to enable the automatic start and stop feature for a serverless RDS instance. After you enable the automatic start and stop feature for the serverless RDS instance, if no connections are established to the serverless RDS instance within 10 minutes, the system automatically suspends the serverless RDS instance. If a connection is established to the serverless RDS instance, the serverless RDS instance automatically resumes. In most cases, it requires approximately 40 seconds to resume the serverless RDS instance, but the duration varies based on the data volume in tables of the serverless RDS instance.

Manual instance startup

If a serverless RDS instance is suspended, you can manually start the instance.

Important
  • The storage capacity that you specified when you create a serverless RDS instance specifies the minimum storage capacity of the serverless RDS instance. The system automatically expands the storage capacity of the serverless RDS instance based on your actual usage. After the storage capacity is expanded, the storage capacity cannot be automatically reduced and you are charged based on the new storage capacity.

  • The system automatically expands the storage capacity of a serverless RDS instance. The system checks the remaining storage every 5 minutes. If the remaining storage is less than 20% of the storage capacity, the system automatically expands the storage capacity based on the larger value between the following items. The storage capacity can be expanded to up to 32 TB.

    • 5 GB

    • 15% of the storage capacity of the serverless RDS instance

Upgrade the RDS edition from RDS Basic Edition to RDS High-availability Edition

If a serverless RDS instance runs RDS Basic Edition, you can upgrade the RDS edition to RDS High-availability Edition.

Billing rules

You are not charged for the upgrade operation. After the upgrade, you are charged based on the pricing for RDS High-availability Edition.

Procedure

  1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
  2. In the Configuration Information section, click Modify Scaling Settings.

  3. In the panel that appears, set the Edition parameter to High-availability Edition and click OK.

  4. In the dialog box that appears, check the information and click OK.

    Note

    During the upgrade, the serverless RDS instance is in the Upgrading/Downgrading state. After the upgrade is complete, the status of the serverless RDS instance changes to Running.

Change the scaling range of RCUs

RCUs are used to measure the performance of a serverless RDS instance. The system automatically adjusts the number of RCUs for a serverless RDS instance within the range that you specified based on your workloads. You can manually specify the scaling range of RCUs.

Usage notes

If you change the scaling range of RCUs for a serverless RDS instance, a smooth inter-instance migration may be triggered, and jitters that last for a few seconds may occur.

Procedure

  1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
  2. In the Configuration Information section, click Modify Scaling Settings.

  3. In the RDS Capacity Units (RCUs) section of the panel that appears, configure the Minimum and Maximum parameters.

    Note

    The number of RCUs ranges from 0.5 to 32. You can configure the parameters based on your business requirements. The performance of an RCU is equivalent to that of an RDS instance that runs RDS Basic Edition and has 2 GB of memory.

  4. Click Ok.

Change the scaling policy

In most cases, the RCU scaling for a serverless RDS instance immediately takes effect and does not affect your workloads. In some special cases, the system may fail to scale the RCUs. In this case, you can modify the scaling policy of the instance to forcefully scale the RCUs.

Description

The following table describes the scaling policies that are supported for a serverless RDS instance.

Scaling policy

Description

Do Not Execute Forcefully

The default scaling policy of the RCUs for the serverless RDS instance. If the RCU scaling triggers an instance switchover, the scaling request is ignored. This scaling policy ensures that no instance switchovers occur when RCUs are scaled. However, this scaling policy cannot ensure the optimal performance of the serverless RDS instance.

Execute Forcefully

After the system receives a scaling request, the system performs scaling even if an instance switchover is triggered. The system forcefully scales the RCUs regardless of the instance status. In this case, an instance switchover occurs. This scaling policy ensures optimal performance. However, this scaling policy cannot ensure the availability of the serverless RDS instance.

Procedure

  • You can specify a scaling policy for a new serverless RDS instance during instance creation. For more information, see Create a serverless ApsaraDB RDS for MySQL instance.

  • To change the scaling policy of an existing serverless RDS instance, perform the following steps:

  1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
  2. In the Configuration Information section, click Modify Scaling Settings.

  3. Click Advanced Settings. Select Execute Forcefully from the scaling policy drop-down list. Then, click OK.

    Important

    An instance switchover may occur during the RCU scaling. Make sure that your application is configured to automatically reconnect to the serverless RDS instance. For more information about the impacts of an instance switchover, see Impacts of an instance switchover.

Configure automatic start and stop

For more information, see Configure automatic start and stop for a serverless ApsaraDB RDS for MySQL instance.

Manually start a serverless RDS instance

If your serverless RDS instance is suspended, you can use the following methods to manually start the instance:

  • Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region in which the serverless RDS instance resides. Then, find the serverless RDS instance and click More in the Actions column. Then, click Start Instance in the drop-down list that appears.

  • Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region in which the serverless RDS instance resides. Then, find the serverless RDS instance and click the instance ID. In the Status section of the Basic Information page, click Start Instance.