Note
For V4.2.1, this parameter is available starting with V4.2.1.
Description
ttl_thread_score specifies the weight of the thread time slice for TTL tasks.
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
The
systenant and user tenants can modify this parameter.
Attributes
| Attribute | Description |
|---|---|
| Type | Int |
| Default value | 0 indicates the default number of threads, which is 2 by default. |
| Value range | [0, 100] |
| 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
You can modify the weight of the TTL DAG thread to change the proportion of the thread time slice for TTL tasks. If the speed of TTL task execution is too slow, you can increase the value of ttl_thread_score appropriately. We recommend that you double the value each time.
Examples
The sys tenant sets the weight of the thread time slice for TTL tasks to 4 in all user tenants.
obclient> ALTER SYSTEM SET ttl_thread_score = 4 tenant = all_user;