You can adjust tenant specifications to scale tenant resources. This topic describes how to modify the specifications of a tenant under a cluster instance.
Scaling scenarios
Check whether the tenant performance meets current requirements. When performance is low, increase the tenant specifications. When resource utilization is too low, reduce the tenant specifications.
Background information
Tenant scaling can increase or decrease computing power and storage capacity. OceanBase Cloud supports scaling by modifying the unit specification and the number of units for a tenant.
Resource unit (Unit)
The unit is a crucial concept in tenant management. OceanBase Cloud manages physical resources based on units, which are collections of physical resources such as CPU, memory, storage space, and IOPS. The unit is also the basic unit for resource scheduling. It has location attributes such as node, zone, and region. A node is an abstraction of a server, a zone is an abstraction of a data center, and a region is an abstraction of a geographic area. By adjusting the location attributes of a unit, you can adjust the deployment mode of a tenant.
Modify unit specification
Increasing or decreasing the unit specification adjusts the service capability of a single replica.
Modify the number of units
Adjusting the number of service nodes: Since a tenant can have only one unit on a node at a time, if the instance is deployed with a single replica, you must first increase the number of nodes and then adjust the number of units.
CPU adjustment rules
When you create a tenant or adjust its CPU specification, ensure that the unallocated CPU capacity of the current instance is greater than or equal to the tenant's minimum CPU specification. The minimum CPU specification for a tenant is 1C.
Memory adjustment rules
When you create a tenant or adjust its memory specification, ensure that the unallocated memory capacity of the current instance is greater than or equal to the tenant's minimum memory specification. The minimum memory specification for a tenant is 4GiB.
Prerequisites
Before modifying tenant specifications, perform the following checks. You can proceed with the modification only if the following conditions are met.
The current tenant is in the Running state.
The cluster instance to which the current tenant belongs is in the Running state.
Procedure
You can modify tenant specifications through the following two approaches:
Approach 1: Log in to the OceanBase Cloud console. On the Tenants page, click the more icon ··· in the Actions column of the target tenant and select Modify Specification.
Approach 2: Log in to the OceanBase Cloud console. In the upper-right corner of the tenant workspace, click the more icon ··· and select Modify Specification.
The following procedure uses Approach 1 as an example:
Log in to the OceanBase Cloud console.
In the left-side navigation pane, click Instances.
In the instance list, find the target cluster instance and click its name to enter the instance workspace.
In the left-side navigation pane, click Tenants.
In the Tenants list, click the more icon ··· in the Actions column of the target tenant and select Modify Specification.
Select the required number of resource units and unit specifications, then click OK to complete the modification.
Note
- When you downgrade a tenant's specification, if the target specification is below the safe memory threshold for downgrading, memory reclamation will be triggered, which may increase request latency and cause performance fluctuations. If memory reclamation cannot reduce the memory to the selected specification, the memory specification will automatically adjust to the safe memory threshold for downgrading.
- If the IOPS setting is available for your AWS BYOC instance, you can adjust the tenant’s IOPS limit.
What to do next
After completing the scaling operation, you can go to the tenant workspace to view the tenant's specification size.