Help Center > > User Guide> Working with RDS for MySQL> Instance Management> Changing a DB Instance Class

Changing a DB Instance Class

Updated at: May 26, 2020 GMT+08:00

Scenarios

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

Currently, the instance classes of only MySQL DB instances billed in the pay-per-use mode can be changed automatically within the maintenance period.

  • A DB instance cannot be deleted while its instance class is being changed.
  • Instance classes of ultra-high performance (advanced) DB instances can only be changed to ultra-high performance (advanced) instance classes.
  • You can scale up or down the compute and memory capacity of MySQL DB instances as required.

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 RDS. 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.

    Figure 1 Changing a DB instance class

    You can change the DB instance class as required.

    Changing the DB instance class will cause the DB instance to reboot. Select off-peak hours to avoid service interruption.

    If you have selected In maintenance window for Scheduled Time, the DB instances will be rebooted during the instance class change time and services will be interrupted. To prevent service interruption, you are advised to set the maintenance window to off-peak hours. For details, see Changing the Maintenance Window.

    DB instances in a DeC only support the general-enhanced instance class.

  6. Confirm the specifications.

    • If you need to modify your settings, click Previous.
    • For pay-per-use DB instances, click Submit.

      To view the cost incurred by the DB instance class change, choose Billing > My Orders in the upper right corner.

  7. View the DB instance class change result.

    • Changing the DB instance class takes 5–15 minutes. During this period, 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.
    • If you have selected Upon submission for Scheduled Time, return to the Instance Management page and view the DB instance status. During the change period, the instance 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.
    • If you have selected In maintenance window for Scheduled Time, return to the Instance Management page and choose Task Center in the navigation pane on the left. On the Scheduled Tasks page, view the execution progress and result of the task.

    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.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel