This topic describes how to change the specifications of a PolarDB for PostgreSQL cluster.
Prerequisites
You can change the specifications of a cluster only if no other specification change is in progress.
Background
PolarDB supports capacity scaling in three dimensions:
-
Vertical scaling of compute resources: Scale cluster specifications up or down.
-
Horizontal scaling of compute resources: Add or remove read-only nodes. For more information, see Add or remove nodes.
-
Horizontal scaling of storage: Depending on the storage type and billing method, storage automatically scales as your data volume changes. You can also manually scale up storage. For more information, see Manually scale up storage.
Billing for configuration changes
For pricing details, see Billing for specification changes.
Usage notes
-
For a centralized PolarDB for PostgreSQL cluster (whose Database Edition is Enterprise Edition or Standard Edition), you can scale up or scale down the specifications of the entire cluster or a single node in the cluster.
NoteWhen scaling the specifications of a single node, ensure that one read-only node has the same specifications as the primary node. You can configure the specifications of other nodes as needed.
-
For a PolarDB for PostgreSQL (Distributed Edition) cluster, you can change specifications only in a uniform manner for all compute nodes (CNs) or all data nodes (DNs). You cannot change the specifications of a single compute node or data node, nor can you change the specifications of an individual read-write (RW) or read-only (RO) node within a compute or data node.
-
Changing specifications takes about 5 minutes per compute node. For example, changing the specifications for a two-node cluster takes about 10 minutes. The total duration also depends on factors such as database load and the number of databases and tables.
-
Scaling cluster specifications up or down does not affect the existing data in the cluster.
-
During a specification change, a connection disruption of up to 30 seconds may occur for each connection endpoint. Perform this operation during off-peak hours and ensure your application has an automatic reconnection mechanism.
Procedure
-
Log on to the PolarDB console.
-
In the upper-left corner of the console, select the region where the cluster is located.
-
Go to the Change Configuration page in one of the following two ways:
-
Find the destination cluster and click Change Configuration in the Operation column.
-
Find the destination cluster and click the cluster ID. On the Basic Information page, click Change Configuration.
-
-
Select Upgrade or Downgrade, and then click OK.
NoteOnly subscription clusters support Temporary Upgrade. For more information, see Temporary Upgrade.
-
On the Change Specifications page, set the following parameters:
Parameter
Description
Sub-series
Select a destination sub-series for the cluster after the upgrade. The default value is Dedicated.
Node Specifications
Select the destination node specifications for the current node.
NoteMake sure that the specifications of one read-only node are the same as the primary node. You can configure the specifications for other nodes as needed.
Switchover Time
Set Switching Time to Switch Now or Scheduled Switch.
If you select Scheduled Switch, you can select a point in time within the next 24 hours. The configuration upgrade task will be completed within 30 minutes after the selected time. You can also view the details of the task or cancel the task on the Scheduled Tasks page. For more information, see Scheduled tasks.
-
Read and select the Terms of Service, and click Buy Now.
-
On the Pay page, confirm the order information and click Purchase.
NoteThe specification change takes effect in about 10 minutes.
API reference
|
API |
Description |
|
Changes the node specifications of a PolarDB cluster. |