vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/dds/umn/en-us_topic_0104721795.html
Wang , Deng Ke 519944c837 DDS UMN 20221101 version 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com>
Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
2022-11-24 09:05:29 +00:00

3.4 KiB
Raw Permalink Blame History

Changing the CPU or Memory of a Replica Set DB Instance

Scenarios

This section guides you on how to change the CPU or memory of your replica set instance.

  • A DB instance cannot be deleted when you are changing its CPU or memory.
  • Instances can be both scaled up and 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.

Procedure

  1. Log in to the DDS console.
  2. On the Instance Management page, locate the target replica set instance and choose Change Instance Class in the Operation column.
  3. On the displayed page, modify required parameters and click Submit.
  4. View the DB instance CPU or memory modification 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 25 to 30 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 replica set instance you scaled up and check whether the scaling up is successful in the DB Information area.