Note
For V2.2.30, this parameter is available starting with V2.2.30.
Description
resource_hard_limit specifies the over-subscription ratio of CPU resources. If the value is greater than 100, over-subscription is allowed.
Privilege requirements
Query the parameter
The
systenant and all user tenants can query this parameter by using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.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 OceanBase Database V4.0.0.0, you cannot configure over-subscription of memory resources by using the
resource_hard_limitparameter.resource_hard_limitspecifies the over-subscription ratio of CPU resources of an OBServer node. On an OBServer node, the sum of theMAX_CPUvalues of all tenant units cannot exceed the over-subscribed CPU capacity:CPU_CAPACITY * resource_hard_limit.If you set
resource_hard_limitto a value greater than 100, the over-subscription takes effect only on the CPU resources of the corresponding resource unit, not on the CPU resources of other resource units. However, when you enable over-subscription, you must ensure that the load of the resource unit can be staggered to avoid system issues caused by the combination of over-subscription and resource overload.
Examples
Set the over-subscription ratio of CPU resources to 100.
obclient> ALTER SYSTEM SET resource_hard_limit = 100;