Changing the CPU or Memory of a Replica Set DB Instance

Scenarios

This section describes 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 scaled up or down.
• When the CPU and memory specifications are changed, a primary/secondary switchover may occur once or twice and the database connection will be interrupted for up to 30s. You are advised to change the specifications during off-peak hours to reduce impacts and ensure that the service system of your client can reconnect to the database if the connection is interrupted.

Procedure

1. Log in to the DDS console.
2. On the Instance Management page, locate the target replica set instance and choose More > Change Instance Class in the Operation column.
3. On the displayed page, modify required parameters and click Next.
4. On the displayed page, confirm the instance class.
   • 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 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.