All Products
Search

This Product

    PolarDB:Temporary upgrade

    Document Center

    PolarDB:Temporary upgrade

    Last Updated:Jun 20, 2026

    A temporary upgrade increases the specifications of an entire cluster or individual nodes for a limited time. When the specified Restore Time is reached, the specifications automatically revert to their original state. PolarDB subscription clusters support temporary upgrades to manage short-term workload peaks.

    Prerequisites

    • The cluster must be a subscription cluster.

    • The cluster must not have any pending orders for renewal, configuration changes, or temporary upgrades.

    Limitations

    • Temporary downgrades are not supported.

    • During the upgrade and scale-back processes, a transient connection interruption may occur. Ensure that your application has a reconnection mechanism.

    • The Restore Time must be at least one day before the cluster's expiration date. For example, if a cluster expires on January 10, the latest Restore Time is January 9.

    • During a temporary upgrade, automatic scaling and adding or removing nodes are not supported. If you need these features, you must make the temporary upgrade permanent.

    • While a temporary upgrade is active (the cluster is in the running state), you can perform a manual upgrade. For more information, see Change Configurations.

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

    • If performance remains insufficient or you need to extend the duration, you can perform one additional upgrade before the original Restore Time. The new Restore Time cannot be earlier than the original one.

    Make a temporary upgrade permanent

    If you need to keep the upgraded specifications, you can make the temporary upgrade permanent while it is active (the cluster is in the running state) to prevent it from automatically scaling back. To do this, perform a manual upgrade to the current specifications on the Upgrade page.

    Note

    This operation does not affect your services.

    Different specifications for primary and read-only nodes

    You can temporarily upgrade the specifications for the primary and read-only nodes of a PolarDB cluster separately, allowing their specifications to differ.

    Limits

    • In 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 those of the primary node:

      • The memory of a read-only node must not be less than half the memory of the primary node.

      • The following table lists the CPU core requirements for read-only nodes relative to the primary node.

        Primary node CPU (cores)

        Minimum read-only node CPU (cores)

        2

        2

        4

        4

        8

        4

        16

        8

        32

        16

        64

        32

        88

        32

    Billing

    The fee for an N-day temporary upgrade is calculated as follows: Fee = (Monthly subscription price for new specifications - Monthly subscription price for 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 then find the cluster.

    2. Open the Change Configurations (Subscription) page in one of the following 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 (Subscription) page, select Temporary Upgrade and click OK.

      Note

      Temporary Upgrade is available only for subscription clusters.

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

      Parameter

      Description

      Specification Type

      Select the target specification type for the cluster after the upgrade. The default value is Dedicated.

      Node

      Select the target specifications for the node after the upgrade.

      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.

      PolarProxy Type

      Select the PolarProxy type for the cluster after the upgrade. The default value is Dedicated Enterprise.

      Restore Time

      Select the expiration time for the temporary upgrade. When this time is reached, the cluster's specifications are automatically restored.

      Note

      • If performance remains insufficient, you can perform one more upgrade before the original Restore Point. The new Restore Time cannot be earlier than the original one.

      • The minimum duration for a temporary upgrade is 1 hour. We recommend a duration of 14 days or less, as the Restore Time cannot be changed once set.

      • The Restore Time must be at least one day before the cluster's expiration date.

    5. Agree to the terms of service, and then click Buy Now.

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