OceanBase Cloud supports adding or deleting nodes and adjusting compute and storage specifications for pay-as-you-go cluster instances to enable scaling.
Calculation formula
The minimum value for storage scale-down is the current usage multiplied by 130%. The minimum value for storage scale-up is the storage size of the current order.
Prerequisites
Only project administrators can perform cluster configuration changes.
Before adding nodes or increasing compute capacity, check how many additional vCPUs your EC2 quota allows in the target Region. If you need more, request a quota increase and verify that it has taken effect before proceeding. For details, see Prepare BYOC instance quotas.
Before adding or deleting nodes or adjusting compute and storage configurations, perform the following checks. Configuration changes can only be made if all conditions are met.
- The current cluster is in the Running state.
- All tenants in the current cluster are in the Running state.
- The current cluster is billed on a pay-as-you-go basis.
Note
- Setting storage scale-down or specification scaling may cause momentary disconnections lasting a few seconds. To ensure business stability, we recommend that you perform this operation during off-peak hours.
- Setting storage scale-up or adding/deleting nodes will not affect your business. However, to ensure business stability, we still recommend that you perform this operation during off-peak hours.
Add or delete nodes
Log in to the OceanBase Cloud console.
In the left-side navigation pane, click Instances.
In the cluster list, find the target cluster, and click Change Configuration in the Actions column.
On the Change Instance Configurations page, click Change Nodes, and specify the node distribution configuration for the cluster from the drop-down list.
In the Summary section on the right side of the page, confirm the configuration information. Read and agree to the relevant agreements (including the End User Agreement, Cloud Service SLA, and Data Collection Agreement), then click Confirm Order.
On the instance list page, you can view the configuration status of the cluster. You can initiate a new configuration change task only after the current one is completed.
Adjust compute and storage configurations
Notice
- AWS imposes a cooldown period for storage capacity changes. If your instance is deployed on AWS, you must wait at least 6 hours after changing the storage capacity or the number of vCPUs and memory before making another change.
- If an instance has a primary-standby relationship, when the primary instance is configured, its resources are matched with those of the standby instance for verification. The target configuration must meet the following conditions: Standby instance CPU >= Primary instance CPU/3, Standby instance memory >= Primary instance memory/3, Standby instance storage >= Primary instance storage. If the standby instance's resources are insufficient, perform a scale-out configuration change for the standby instance first.
Log in to the OceanBase Cloud console.
In the left-side navigation pane, click Instances.
In the cluster list, find the target cluster and click Change Configuration in the Actions column.
On the Change Instance Configurations page, click to select Change Compute and Storage.
Configure the required Compute and Storage.
Note
- If your instance is V4.x or later and you are upgrading the specification and storage, you can choose the in-place configuration change method. This allows you to directly modify the existing database instance's specifications, such as CPU, memory, and storage space, without interrupting database services. However, in-place configuration change may pose stability risks and increase short-term latency. Avoid performing this operation during business peak hours.
- When downgrading, ensure that the maximum IOPS supported by the target configuration is greater than or equal to the current tenant's allocated IOPS resource limit.
In the Summary section on the right side of the page, confirm the configuration information, read and agree to the relevant agreements (including the End User Agreement, Cloud Service SLA, and Data Collection Agreement), then click Confirm Order.
On the cluster list page, you can view the configuration change status of the cluster. You can initiate a new configuration change task only after the current one is completed.