Help Center> Document Database Service> User Guide> Instance Management> Changing the CPU or Memory of a Single Node DB Instance
View PDF

Changing the CPU or Memory of a Single Node DB Instance

Scenarios

This section describes how to change the CPU or memory of your single node instance.

  • You can change the CPU and memory of a DB instance only when your account balance is greater than or equal to ¥0.
  • A DB instance cannot be deleted when you are changing its CPU or memory.
  • Instances can be scaled up or down.
  • Services will be interrupted for 5 to 10 minutes when you change DB instance CPU and memory. You are advised to perform this operation during off-peak hours. After the restart is complete, the cached memory will be automatically cleared. The DB instance needs to be warmed up to prevent congestion during peak hours.

Precautions

  • Instances in pay-per-use mode are still charged based on the time used after the instance CPU or memory is changed.
  • If you change the CPU or memory of a yearly/monthly DB instance, you will pay price difference or get a refund.
    • If you scale up the instance class, you need to pay extra fee based on the period in which instances are put into use.
    • If you scale down the instance class, you will get a refund based on the period in which instances are put into use. The refund will be sent to your account. You can click Billing Center in the upper right corner of the console to view your account balance.

Procedure

  1. Log in to the DDS console.
  2. On the Instance Management page, locate the target single node instance and choose More > Change Instance Class in the Operation column.
  3. On the displayed page, modify required parameters and click Next.

    Figure 1 Scale Single Node

  4. On the displayed page, confirm the instance class.

    • Yearly/Monthly
      • If you need to modify your settings, click Previous to go back to the page for you to specify details.
      • If you do not need to modify your settings, click Submit to go to the payment page and complete the payment.
    • Pay-per-use
      • If you need to modify your settings, click Previous to go back to the page for you to specify details.
      • If you do not need to modify your settings, click Submit to change the instance class.

  5. View the DB instance class change result.

    • When the CPU or memory of a DB instance is being changed, the status displayed in the Status column is Changing instance class. This process takes about 10 minutes.
    • In the upper right corner of the DB instance list, click to refresh the list. The instance status changes to Available.
    • Go to the Basic Information page of the single node you scaled up and check whether the scaling process is successful in the Configuration area.

Parent topic: Instance Management