Configure temporary scaling

更新时间:
复制 MD 格式

Change the configuration of a subscription cluster instance to accommodate temporary business fluctuations.

Notes

Note the following when you use temporary scaling:

  • You cannot change the standard configuration of a cluster instance that is using a temporary capacity.

  • You cannot configure automatic storage scaling for a cluster instance that is using a temporary capacity.

  • You cannot add standby instances to a cluster instance that is using a temporary capacity.

  • You cannot switch to the pay-as-you-go billing method for a cluster instance that is using a temporary capacity.

  • You cannot change the deployment type of a cluster instance that is using a temporary capacity.

  • After a temporary scaling, incremental fees are incurred and charged hourly during the scaling period. For more information, see Temporary scaling billing.

  • If the temporary configuration matches the original configuration, the temporary scaling operation ends and incremental fees are no longer charged.

Note

Enabling temporary scaling may cause transient disconnections. We recommend that you perform this operation during off-peak hours.

Prerequisites

Before you configure temporary scaling, ensure that the following requirements are met:

  • The cluster is in the Running state.

  • All tenants in the cluster are in the Running state.

  • The billing method for the cluster is subscription.

Procedure

  1. Log on to the OceanBase console .

  2. In the navigation pane on the left, click Instance List.

  3. In the instance list, find the target cluster instance and click the instance name to open the Cluster Instance Workspace.

    Note

    Only subscription Standard Edition (Cloud Disk) cluster instances support temporary scaling.

  4. In the upper-right corner, click the More icon and then click Temporary Scaling.

  5. In the dialog box that appears, select the type of configuration change.

    Parameter

    Description

    Temporary upgrade/downgrade

    A temporary upgrade or downgrade may cause transient disconnections. Ensure that your application has a reconnection mechanism. Perform this operation during off-peak hours.

    Convert to permanent storage

    This option is available after you configure a Temporary upgrade/downgrade. After you convert to permanent storage, both the storage and specifications become permanent resources. The billing mode changes to the billing rule for permanent resources.

    Convert to permanent specifications

    This option is available after you configure a Temporary upgrade/downgrade. After you convert to permanent specifications, the billing mode for specifications changes to the billing rule for permanent specifications.

    image

    Note

    If you access the temporary scaling feature for the first time, you can only select Temporary Upgrade Or Downgrade.

  6. Complete the subsequent operations based on the selected scenario:

    • If you select Temporary Upgrade/Downgrade, set the Specifications and Capacity, and then click OK.

      Note
      • ApsaraDB for OceanBase does not support temporary downgrades of the original specifications of a cluster.

      • The capacity can be adjusted in increments of 5 GB.

      image

    • If you select Convert To Permanent Storage, set the Storage Size, select the Terms of Service check box, and click Buy Now. For more information about billing rules, see Pricing.

      image

    • If you select Convert To Permanent Specifications, set the Node Specifications, Storage Size, and Log Disk Size, select the Terms of Service check box, and then click Purchase Now. For more information about the billing rules, see Pricing.

      image

  7. After the temporary scaling is complete, you can view the related information on the Cluster Instance Workspace page.

    变配后..png