This topic describes how to upgrade or downgrade the specifications of a PolarDB cluster. It takes only 5 to 10 minutes for the new specifications of each node to take effect.
Prerequisites
You can change cluster specifications only when the cluster does not have pending specification changes.
Background information
This topic describes how to change the specifications of a cluster to meet your business requirements. PolarDB supports capacity scaling in three dimensions:
- Vertically scale the computing capacity: Upgrade or downgrade the specifications of the cluster. This topic describes the details of vertically scaling.
- Horizontal scaling of computing capabilities: Add or remove read-only nodes. For more information, see Add or remove a read-only node.
- Horizontal scaling of storage capacity: The storage capacity is provisioned in a serverless model. The storage capacity is automatically scaled based on the amount of data.
Configuration change fees
For more information, see Configuration change fees.
Precautions
- You can upgrade or downgrade only clusters. You cannot upgrade or downgrade a single node in a cluster.
- When you upgrade or downgrade a cluster, data stored in the cluster is not affected.
- During the upgrade or downgrade process, your applications are temporarily disconnected from each endpoint for no more than 30 seconds. We recommend that you upgrade or downgrade your cluster during off-peak hours and make sure that your applications are configured with the automatic reconnection mechanism.
Procedure
Related API operations
Operation | Description |
---|---|
ModifyDBNodeClass | Changes the node specifications of a PolarDB cluster. |