Note
This parameter is available starting with V2.2.50.
Description
resource_hard_limit specifies the overcommit percentage of CPU resources.
Privilege requirements
Query the parameter
The
systenant and all user tenants can use theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview to query this parameter.Modify the parameter
Only the
systenant can modify this parameter. User tenants cannot modify this parameter.
Attributes
| Attribute | Description |
|---|---|
| Type | Int |
| Default value | 100 |
| Value range | [100, 10000] |
| Modifiable | Yes. You can use the ALTER SYSTEM SET statement to modify the parameter. |
| Effective upon OBServer node restart | No. The setting takes effect immediately. |
Considerations
Starting from V4.0.0.0, OceanBase no longer supports memory resource overselling via the
resource_hard_limitconfiguration item.resource_hard_limitis used to adjust the overselling ratio ofCPU_CAPACITYon an OBServer node. On an OBServer node, the totalMAX_CPUof all tenant Units must not exceed the oversold CPU capacity:CPU_CAPACITY * resource_hard_limit.If
resource_hard_limit > 100is set, after overselling takes effect, only the upper limit of the corresponding resource unit (CPU) is affected; the lower limit of the resource is not affected. However, extra caution is required when using the overselling mechanism. Ensure that workloads can utilize resources at different times to avoid system issues caused by the combination of heavy workloads and resource overselling.
Examples
Set the overcommit percentage of CPU resources to 100.
obclient> ALTER SYSTEM SET resource_hard_limit = 100;
