This topic describes the MetaDB resources required for deploying OceanBase Cloud Platform (OCP).
CPU and memory
MetaDB stores the persistent data other than monitoring data and requires relatively few resources. We recommend that you allocate 4 CPU cores and 8 GB of memory to the MetaDB tenant.
| Number of managed OBServers | CPU (core) | Memory (GB) |
|---|---|---|
| ≤ 10 | 4 | 8 |
| ≤ 50 | 8 | 16 |
| ≤ 100 | 16 | 32 |
| ≤ 200 | 32 | 64 |
| ≤ 400 | 64 | 128 |
We recommend that you create a separate tenant in OceanBase Database for MetaDB. SQL commands for tenant resource allocation:
Create resource unit ocp_unit_config min_cpu=x,
max_cpu=x,min_memory=xxxxx,
max_memory=xxxxx,
max_iops=1000,
min_iops=1000,
max_disk_size=1000000000,
max_session_num=100;
create resource pool ocp_pool unit='ocp_unit_config', zone_list=('test1','test2','test3'),unit_num=x;
create tenant ocp_meta resource_pool_list = ('ocp_pool');
Disk space
The disk space required depends on factors such as the size of the managed cluster, stored files, and the data retention period. We recommend that you reserve at least 100 GB of disk space. When the available disk space of a tenant is insufficient, you can scale out the tenant as required.
Log on to the OCP console. On the Cluster Overview page, click the name of the cluster for MetaDB in the Clusters list.
In the upper-right corner of the Overview page, click Add OBServer .
In the dialog box that appears, add a host.
In the left-side navigation pane, click Tenant Management and select the tenant that you want to scale out.
In the Replica Details section of the Overview page, click Edit for the zone you want to modify.
Change the number of units and click OK .