A temporary upgrade increases the specifications of your cluster for a specified period. You can upgrade the specifications of an entire cluster or a single node. When the specified revert time is reached, the cluster's specifications automatically revert to their original state. PolarDB subscription clusters support temporary upgrades to help you handle short-term traffic peaks.
Applicability
The cluster is a subscription cluster.
The cluster has no pending orders for renewal with specification change or temporary upgrade.
PolarDB for PostgreSQL Distributed Edition clusters are not supported.
Notes
Temporary downgrades are not supported.
The temporary upgrade and revert processes may cause a transient disconnection that lasts for approximately 20 to 30 seconds. Before the switch, ensure that your application has a reconnection mechanism.
The revert time cannot be later than one day before the expiration date of the cluster. For example, if a cluster expires on January 10, the latest revert time for a temporary upgrade is January 9.
During a temporary upgrade, you cannot automatically change specifications or add or delete nodes. To perform these operations, you must first make the temporary upgrade permanent.
During a temporary upgrade, you can manually upgrade the cluster again while it is in the running state. For more information, see Manual upgrade.
The minimum duration for a temporary upgrade is 1 hour. The recommended maximum duration is 14 days.
If performance is insufficient after a temporary upgrade or to extend the revert time, you can perform another upgrade before the revert time is reached. The new revert time cannot be earlier than the original one.
Make a temporary upgrade permanent
If you want to retain the upgraded specifications, you can make the temporary upgrade permanent during the upgrade period while the cluster is running. This prevents the cluster from being automatically downgraded after the revert time. To do this, go to the Upgrade page and perform a manual upgrade to the current specifications.
This operation does not affect your services.
Upgrade primary and read-only nodes separately
PolarDB clusters allow you to temporarily upgrade the specifications of primary and read-only nodes separately. This means that the specifications of a read-only node can differ from the specifications of the primary node.
In the same cluster, ensure that at least one read-only node has the same specifications as the primary node.
The specifications of read-only nodes cannot be significantly different from the specifications of the primary node:
The memory of a read-only node cannot be less than half of the primary node's memory.
The following rules apply to the CPU specifications of read-only nodes relative to the primary node:
Primary node CPU specifications (cores)
Minimum allowed CPU specifications for read-only nodes (cores)
2
2
4
4
8
4
16
8
32
16
64
32
88
32
Billing
The price of a temporary upgrade is 1.5 times the price difference between the new and old configurations. The formula is as follows:
Cost of a temporary upgrade for N days = (Monthly price of new specifications - Monthly price of old specifications) / 30 × 1.5 × N.
Procedure
Log on to the PolarDB console. In the navigation pane on the left, click Clusters. Select the region where the cluster is located, and then find your cluster.
Go to the Change Configurations page in one of the following two ways:
In the Actions column of the cluster, click Change Configurations.
Click the cluster ID to go to the Basic Information page. In the Database Nodes section, click Change Configurations.
On the Change Configurations page, select Temporary Upgrade and click OK.
In the dialog box that appears, set the following parameters.
Parameter
Description
Sub-series
Select the target sub-series for the cluster after the upgrade. Options include General-purpose and Dedicated.
Node
Select the target node specifications for the current node after the upgrade.
NoteMake sure one read-only node has the same specifications as the primary node. You can configure the specifications for other nodes as needed.
Database Proxy Type
The database proxy type after the cluster upgrade. The default value is Dedicated Enterprise Edition.
Revert Time
Select the time when the temporary upgrade expires and reverts.
NoteIf performance is insufficient after the temporary upgrade, you can perform one more upgrade before the revert time is reached. The new Revert Time cannot be earlier than the original one.
The minimum duration for a temporary upgrade is 1 hour. Because the revert time cannot be changed after it is set, we recommend a maximum upgrade duration of 14 days.
The revert time cannot be later than one day before the cluster's expiration date.
Select the Terms of Service and click Buy Now to complete the payment.
On the Payment page, confirm the order and click Purchase.