Modify package specifications

Background information

Modifying package specifications is supported only for instances of the Standard Edition (Cloud Disk) series. You can scale out tenant instances to a maximum of 2 cores and 8 GB of memory, or scale them in to a minimum of 1 core and 4 GB of memory.

You can modify package specifications using two methods: migration-based change and in-place change. Choose the method that suits your business needs.

• Migration-based change: A new node with the target specifications is created. Data is migrated and synchronized to the new node. A failover to the new node completes the change. The time required for this process depends on the data volume of the cluster.

• In-place change: Traffic is temporarily switched to another node. The specifications of the original node are then modified. After the modification, traffic is switched back. This method is fast because it does not require full data migration. Network latency may increase on the node while its specifications are being changed.

Prerequisites

Before you modify package specifications, ensure that the following conditions are met.

• The cluster is in the Running state.

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

• The cluster is not in a temporary capacity state.

Procedure

Cluster instances

1. Log on to the OceanBase Management Console .

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

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

4. Click the More icon in the upper-right corner, and then click Standard Upgrade/Downgrade.

   

5. Click Change Specifications. In the Select Target Specifications section, select your desired specifications.

   

   1. If the package is already at its maximum specifications, you cannot scale it out.

   2. If the package is at its minimum specifications, or if the resources allocated to tenants exceed the next smaller cluster specifications, you cannot scale it in.

      Note

      • Only V4.x cluster instances can be downgraded to a minimum of 4 cores and 16 GB of memory.

      • Currently, only V4.x cluster instances support in-place changes.

      • The log disk capacity is also a condition for scaling in a cluster. The following rule applies:

        You cannot scale in a cluster to the target specifications if the log disk space allocated to its tenants exceeds (memory capacity of the target specifications × 1.8) + 5 GB. If this occurs, go to the Tenant Workspace to adjust the tenant's log disk size. After the size meets the requirement, you can scale in the cluster. If you cannot adjust the log disk size, contact OceanBase technical support.

6. Click OK.

7. Check the current configuration. Select the required storage size, and then check the Terms of Service checkbox.

8. Click Buy Now and complete the payment.

Tenant instances

1. Log on to the OceanBase Management Console.

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

3. In the instance list, click the name of the target tenant instance to open the Tenant Instance Workspace.

4. In the upper-right corner, click the More icon, and then select Standard Upgrade/Downgrade.

5. In the dialog box, click Scale Out Package Specifications or Scale In Package Specifications.

6. Click OK.

7. Select the node specifications to scale out or scale in, and then select the Terms of Service check box.

8. Click Buy Now and complete the payment.

What to do next

After the instance is scaled, you can view its updated package specifications in the Cluster Workspace or Tenant Workspace.