ApsaraDB for OceanBase lets you modify the configurations of cluster and tenant instances. You can perform standard or temporary upgrades and downgrades to scale your instances.
How it works
Compared to traditional single-node databases, the distributed architecture of OceanBase Database provides flexible online extensibility. It supports online scaling while the cluster remains active. When the external payload on a cluster changes, you can adjust its capacity. You can change the number of physical servers in a zone by adding or removing OBServers. You can also change their specifications, such as Central Processing Unit (CPU) and memory.
Cluster instance configuration
OceanBase provides standard and temporary upgrade and downgrade features to implement cluster-level configuration changes.
Standard upgrades or downgrades include scale-out methods, such as storage capacity expansion, package specification upgrades, adding nodes, and log disk expansion. They also include scale-in methods, such as storage capacity reduction, package specification downgrades, and deleting nodes. For more information, see Related links.
Temporary upgrades or downgrades are temporary changes to specifications. After a temporary change, you can make the new storage or package specifications permanent.
Tenant instance configuration
ApsaraDB for OceanBase supports tenant-level scaling. You can adjust Unit specifications and modify the number of Units. For more information, see Related links.
You can adjust Unit specifications to increase or decrease the service capacity of a single node based on your scaling needs. For more information, see Modify tenant resources.
You can modify the number of Units to add service nodes. This provides distributed capabilities and improves the overall performance of the tenant.
Related links
Title |
Description |
Outlines the procedure and notes for modifying storage space. Modify the storage space to scale an instance. |
|
Outlines the procedure and notes for modifying package specifications. Modify the package specifications to scale an instance. |
|
Outlines the procedure and notes for adding or deleting nodes. Add or delete nodes to scale an instance. |
|
Outlines the scenarios and notes for increasing log disk capacity to scale out. Log disk expansion is a feature available only to users on a whitelist. To use this feature, contact the ApsaraDB for OceanBase helpdesk. |
|
Outlines the procedure for enabling automatic storage scaling for a cluster instance. |
|
Outlines the procedure for temporary upgrades or downgrades. You can change the configuration of a subscription cluster instance to meet temporary scaling needs that arise from business fluctuations. |
|
Outlines the procedure for modifying the specifications of a tenant in a cluster instance. |