Changing a DB Instance Class

Scenarios

You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the change is successful.

Constraints

• A DB instance cannot be deleted when its instance class is being changed.
• After you change instance classes, the DB instances will reboot and services will be interrupted. Therefore, you are advised to change instance classes during off-peak hours.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
4. On the Instance Management page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

   Alternatively, click the target DB instance to go to the Basic Information page. In the DB Information area, click Change in the Instance Class field.

5. On the displayed page, specify the new instance class and click Next.

6. View the DB instance class change result.

   Changing the DB instance class takes 5–15 minutes. During this period, you can view the execution progress of Changing a MySQL DB instance class on the Task Center page. The status of the DB instance on the Instance Management page is Changing instance class. After a few minutes, click the DB instance and view the instance class on the displayed Basic Information page to check that the change is successful.

   

   After you change a MySQL instance class, the values of the following parameters will also be changed accordingly: back_log, innodb_buffer_pool_size, innodb_log_buffer_size, innodb_log_files_in_group, max_connections, innodb_page_cleaners, innodb_buffer_pool_instances, threadpool_size, and slave_parallel_workers.