Note
For V4.0.0, this parameter is available starting with V4.0.0.
Description
ha_high_thread_score specifies the number of current working threads for high-priority high-availability tasks.
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
The
systenant and user tenants can modify this parameter.
Attributes
| Attribute | Description |
|---|---|
| Type | Int |
| Default value | 0, indicating that the default number of working threads is 8. |
| 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
In V4.x, tasks related to high availability (HA), such as migration replication and backup and restore, are scheduled and executed by the DagScheduler at the tenant level. To ensure efficient resource utilization, instead of configuring separate parameters for different task types, three HA-related parameters are set based on task priority and importance:
ha_high_thread_score: specifies the number of concurrent threads for high-priority HA tasks such as replication, rebuild, and restore.ha_mid_thread_score: specifies the number of concurrent threads for medium-priority HA tasks such as migration.ha_low_thread_score: specifies the number of concurrent threads for low-priority HA tasks such as backup, backup of backup, and backup cleanup.
Examples
Set the number of current working threads for high-priority high-availability tasks of the current tenant to 10.
obclient> ALTER SYSTEM SET ha_high_thread_score =10;
References
- Set the number of current working threads for high-priority high-availability tasks: ha_mid_thread_score
- Set the number of current working threads for low-priority high-availability tasks: ha_low_thread_score