forked from docs/doc-exports
Wang , Deng Ke
ba65944bfd
Reviewed-by: Boka, Ladislav <ladislav.boka@t-systems.com> Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com> Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
2.2 KiB
2.2 KiB
Changing the DB Instance Class
Scenarios
This section describes how to change the DB instance class.
- A DB instance cannot be deleted when you are changing its instance class.
- Instances can be scaled up or down.
- For cluster and replica set instances, when the DB instance class is changed, a primary/secondary switchover may occur 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 your client can reconnect to the database if the connection is interrupted.
- For a single node instance, services will be interrupted up to 10 minutes when you change DB instance class. 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.