This topic describes the limits on CPU, memory, and log disk specifications for your reference during resource adjustment.
Limits on the CPU specification
When you specify the CPU specification for a new tenant or adjust the specification for an existing tenant, make sure that the number of unallocated CPU cores in the current cluster is greater than or equal to the minimum CPU specification for a tenant.
The minimum CPU specification for a tenant is 2C (2 CPU cores) in OceanBase Database V2.x.
The minimum CPU specification for a tenant is 1C (1 CPU core) in OceanBase Database V3.x.
The minimum CPU specification for a tenant is 1C (1 CPU core) in OceanBase Database V4.x.
Limits on the memory specification
When you specify the memory specification for a new tenant or adjust the specification for an existing tenant, make sure that the size of unallocated memory in the current cluster is greater than or equal to the minimum memory specification for a tenant.
The minimum memory specification for a tenant is 5 GB in OceanBase Database V2.x.
The minimum memory specification for a tenant is 4 GB in OceanBase Database V3.x.
The minimum memory specification for a tenant is 4 GB in OceanBase Database V4.x.
Limits on the log disk specification
When you specify the log disk specification for a new tenant or adjust the specification for an existing tenant, make sure that the size of unallocated log disk space in the current cluster is greater than or equal to the minimum log disk specification for a tenant.
When the memory specification of a tenant is greater than or equal to 4 GB but less than 64 GB, the minimum log disk specification is twice the memory specification.
When the memory specification of a tenant is greater than or equal to 64 GB but less than or equal to 128 GB, the minimum log disk specification is 1.75 times the memory specification.
When the memory specification of a tenant is greater than 128 GB, the minimum log disk specification is 1.5 times the memory specification.
Note
You can adjust the log disk size only in OceanBase Database V4.x or later.