Changing a DB Instance Class

Scenarios

Constraints

• An instance cannot be deleted while its instance class is being changed.
• The following operations cannot be performed on an instance whose instance class is being changed: rebooting the instance, scaling up storage space, modifying the parameter template, creating a manual backup, creating a database account, and creating a database.
• After the instance class is changed, some parameters are automatically changed to the default values defined in the new instance class. The parameters are threadpool_size, innodb_buffer_pool_size, innodb_io_capacity, innodb_io_capacity_max, innodb_buffer_pool_instances, back_log, and max_connections.
• Changing an instance class will interrupt services for about 10 to 120 seconds. Ensure that your applications support automatic reconnection. Perform this operation during off-peak hours because changing an instance class during peak hours takes much more time.
• Changing an instance class takes 5 to 15 minutes.

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.
4. On the Instances 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 next to the Instance Class field.

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

6. Check the change result.

   Return to the Instances page and view the instance status. During the change period, the instance status is Changing instance class. You can view the execution progress of Changing a MySQL DB instance class on the Task Center page. After a few minutes, view the DB instance class on the Basic Information page to check that the change is successful.

   Notice

   After the instance class is changed, the values of the following parameters will 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.