Notice
For V2.2.30, this parameter is available starting with V2.2.30.
Description
resource_hard_limit defines the percentage of CPU resources that can be oversubscribed. If the value exceeds 100, CPU resources are oversubscribed.
Privilege requirements
Query the parameter
You can query this parameter by using the
SHOW PARAMETERSstatement or theGV$OB_PARAMETERSview in thesystenant and all user tenants.Modify the parameter
You can modify the parameter only in the
systenant. User tenants cannot modify the 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
From OceanBase Database V4.0.0.0, you cannot use the
resource_hard_limitparameter to configure the over-subscription of memory resources.resource_hard_limitdefines the overprovisioning ratio ofCPU_CAPACITYof an OBServer node. All theMAX_CPUvalues of tenant units on this OBServer node cannot exceed the total overprovisioned value of CPU capacity. That is,CPU_CAPACITY * resource_hard_limit.If
resource_hard_limit >100, over-subscription is enabled, and only the upper limit of the resources (CPU) of the corresponding resource unit is affected. The lower limit is not affected. However, you must be very cautious when enabling this feature. Make sure that the load can use the resources off-peak to avoid system issues caused by over-provisioning after the load overflows.
Examples
Set the CPU resource oversubscription percentage to 100.
obclient> ALTER SYSTEM SET resource_hard_limit = 100;