Temporary upgrade

Precautions

• Temporary downgrades are not supported.

• A transient connection interruption of about 20 to 30 seconds may occur during the upgrade and reversion processes. Before you proceed, ensure your application has a connection retry mechanism.

• The reversion time cannot be later than one day before the cluster's expiration date. For example, if a cluster expires on January 10, the latest reversion time is January 9.

• Automatic configuration changes and adding or removing nodes are not supported during a temporary upgrade. To perform these operations, you must first convert the temporary upgrade to a permanent upgrade.

• You can perform a manual upgrade while a temporary upgrade is active (when the cluster status is Running). For more information, see Manual upgrade.

• The minimum duration for a temporary upgrade is 1 hour. We recommend a maximum duration of 14 days.

• If performance is insufficient after the upgrade or you need to extend the reversion time, you can perform one more upgrade before the original reversion time is reached. The new reversion time cannot be earlier than the original one.

Convert a temporary upgrade to a permanent upgrade

Modify primary and read-only nodes independently

PolarDB lets you temporarily upgrade the specifications of primary and read-only nodes independently. This means the specifications of a read-only node can differ from those of the primary node.

• Within the same cluster, ensure that at least one read-only node has the same specifications as the primary node.

• We recommend that the specifications of read-only nodes do not differ significantly from the primary node's specifications:

  • The memory of a read-only node cannot be less than half of the primary node's memory.

  • The following table shows the minimum CPU requirements for read-only nodes based on the primary node's CPU specifications.

    Primary node CPU	Minimum read-only node CPU
    2	2
    4	4
    8	4
    16	8
    32	16
    64	32
    88	32

Billing

The cost of a temporary upgrade is 1.5 times the price difference between the new and original configurations. The formula is as follows:

Cost of a temporary upgrade for N days = (Monthly price of new specifications - Monthly price of original specifications) / 30 × 1.5 × N.

Procedure

1. Log on to the PolarDB console. In the left-side navigation pane, click Clusters. Select the region where your target cluster is located, and find your cluster.

2. You can open the Change Configurations page in one of the following two ways:

   • In the Actions column of the target cluster, click Change Configurations.

   • Click the cluster ID to go to the Basic Information page. In the Database Nodes section, click Change Configurations.

     

3. On the Change Configurations page, select Temporary Upgrade and click OK.

4. In the dialog box that appears, set the following parameters.

   Parameter	Description
   Edition	Select the target edition for the cluster after the upgrade. Options include General-purpose and Dedicated.
   Node	Select the target specifications for the node. Note Ensure that at least one read-only node has the same specifications as the primary node. You can configure the specifications for all other nodes as needed.
   Database proxy type	The database proxy type after the upgrade. The default is Enterprise Dedicated Edition.
   Reversion time	Select the time at which the temporary upgrade expires and the specifications revert. Note If performance is insufficient after the temporary upgrade, you can perform one more upgrade before the original reversion time is reached. The new Restore Point cannot be earlier than the original one. The reversion time cannot be changed after it is set. Therefore, we recommend an initial duration of no more than 14 days. The reversion time cannot be later than one day before the cluster's expiration date.

5. Read and accept the terms of service, then click Buy Now.

6. On the Payment page, confirm the order details and click Purchase.