Overview

This article describes how to change the configuration of an instance, including instance specifications and storage space.

For other engine configuration changes, see:

• SQL Server Configuration Change
• PostgreSQL Configuration Change

Considerations

1. Before the configuration change, the optional specifications are the ones currently supported by the availability zone because there is a dynamic change in the availability zone resources.
2. During the effective period of the configuration change, the database stops writing. The writing stop time depends on the business traffic. It is impossible to perform most operations related to the database, account, and network. Please try to perform the configuration change during the low peak period of the business.

3. Since the stand-alone basic version has only one database node and no backup node as a hot backup, it becomes unavailable for a long time when the node is subject to a configuration change. If the business has high requirements for database availability, it is not recommended to use the basic version. Thus, you can choose other series, such as the dual-computer high-availability version.

   Instance type	Product series	Configuration change stage
   Master instance	Standalone basic version	Instance switch-over: To ensure data consistency, the writing stops during the switch-over, and the writing stop time depends on the business traffic. Select the low peak period of the business to avoid massive data change and ensure the business reconnection mechanism.
   	Dual-computer high-availability version	Data migration: The instance access is not affected, the data migration rate is proportional to the data volume and is 100 G/hour. Evaluate the migration time according to the data volume; Instance switch-over: To ensure data consistency, the writing stops during the switch-over, and the writing stop time depends on the business traffic. Select the low peak period of the business to avoid massive data change and ensure the business reconnection mechanism.
   Read-only instance	_	The configuration change of the read-only instance is the same as the master instance. However: Before the configuration change, you need to disable the read traffic of the read-only instance. After the configuration is complete, you need to enable the read traffic again. Configuration change period: The GTID-based replication can maintain data consistency with the instance being not disabled; The instance is unavailable, resulting in the master-slave delay. It is not recommended to use the instance.
   Proxy instance	_	During the configuration change of the proxy instance, you need to change the number of nodes only, but not to copy the data. Therefore, no influence on the service takes place during the change.

   Billing Rules

   After the configuration change of the instance, the billing rules are as follows:

   Billing mode	Description of billing rules
   Postpaid instance	Rules   ? Support the configuration upgrading and downgrading.   ? The resources are billed by the minimum unit of minutes. The duration of less than one minute is counted as one minute. Fees   ? Fees required to pay after the configuration change = New instance configuration fees (CPU, memory, storage disk).
   Prepaid instance	Rules   ? Support the configuration upgrading and do not support the configuration downgrading.   ? The instance is billed by the minimum unit of days, and less than one day is counted as one day.   ? Regardless of whether you can enjoy a prepaid discount for an instance with configuration changed, it depends on whether the remaining time is 1, 2, or 3 years. Fees   ? Fees to be paid after the configuration change = (Remaining days of the contract/Total days of the contract) * (New instance fee - Original instance fee).

   Change Instance Configuration

   1. Log in to RDS Management Console
   2. In the upper left corner of the console page, select the Region where the instance resides.
   3. Find the target instance, and click Instance Name to enter the Instance Details page.

   4. In the "Configuration Information"module, click Configuration Change to enter the configuration change page.

      

   5. This page shows the current configuration of the instance. The user can choose to change the specifications and storage space of the instance.

      Change Items	Description
      Instance specifications	Support the change of the instance specification (CPU, memory combination). Also, you can adjust the specifications as the case may be. The prepaid instances support configuration upgrading, and the postpaid instances support configuration upgrading and downgrading.
      Storage space	Support the increase in the storage space.

   6. Click Next: confirm the changed instance configuration order.
   7. After the confirmation, click "Go to pay" and follow the prompts to complete the payment.

   8. View the changed instance

      • Method I: The user can select "Show Order Details" for order query.
      • Method II: Select the "Management Console" to enter the "Cloud Database RDS - Instance List". The status of the Baidu AI Cloud RDS instance is "Configuration Change in Progress". After the change is complete, the status is restored to "Running".

   FAQs

   1. Why can't the configuration of my RDS instance be changed?

      Answer: The configuration of the RDS instance cannot be changed in the following circumstances:

      • Postpaid instances support instance specification upgrading, downgrading, and memory upsizing but do not support memory downsizing.
      • Prepaid instances support the configuration upgrading of the instance specifications and memory but do not support the configuration downgrading of the instance specifications and memory;