After you create a tenant, you can scale it in by changing its specification. This topic describes how to scale in the tutorial_mysql01 tenant by changing its specification from 2C8GB to 1C4GB. You can scale in a tenant to reallocate resources if its performance exceeds requirements or to create new tenants.
Concepts
Tenant scaling involves increasing or decreasing computing power and storage capacity. ApsaraDB OceanBase supports scaling by changing a tenant's unit specification and the number of units.
Resource Unit (Unit)
A unit is a key concept in tenant management. OceanBase uses units to manage physical resources. A unit is a collection of physical resources, such as CPU, memory, storage capacity, and input/output operations per second (IOPS). A unit is also the basic unit for resource scheduling. It has location properties, such as node, zone, and region. You can modify the deployment of a tenant by adjusting the location properties of its units.
Change Unit Specification
Increasing or decreasing the unit specification adjusts the service capacity of a single node.
Change the Number of Units
This action adjusts the number of service nodes. A tenant can have only one unit on a node at a time. For a single-node cluster, you must add more nodes before you can increase the number of units.
Procedure
In the navigation pane on the left, click Tenant Management to go to the tenant list page.
In the upper-left corner, verify that the cluster status is Running.
In the tenant list, verify that the status of all tenants is Running.
Click Modify Tenant Resources for the tutorial_mysql01 tenant.
In the dialog box that appears, change the Unit Specification to 1C4GB.
Click OK.