Note
For V2.2.30, this parameter is available starting with V2.2.30.
Description
resource_hard_limit specifies the percentage of CPU resources that can be oversold. A value greater than 100 indicates that overselling is allowed.
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 OceanBase Database V4.0.0.0, you cannot use the
resource_hard_limitparameter to oversell memory resources.resource_hard_limitspecifies the percentage of CPU resources that can be oversold on an OBServer node. The sum of theMAX_CPUvalues of all tenants on the OBServer node cannot exceed the oversold CPU capacity:CPU_CAPACITY * resource_hard_limit.If you set
resource_hard_limitto a value greater than 100, the oversold CPU capacity will only affect the upper limit of the corresponding resource units, not the lower limit. However, using the overselling mechanism requires caution to ensure that workloads can stagger their resource usage and avoid system issues caused by resource overloading and overselling.
Examples
Set the percentage of CPU resources that can be oversold to 100.
obclient> ALTER SYSTEM SET resource_hard_limit = 100;