Note
- Due to the architectural optimization of physical backup and restore in V4.x, this parameter is removed starting from V4.0.0.
- In V4.x, three high-availability-related parameters are introduced based on the priority and importance of tasks. Each parameter corresponds to a different task type:
ha_high_thread_score: specifies the number of working threads for high-priority high-availability tasks such as replication, rebuild, and restore. For more information about the tenant-level parameterha_high_thread_score, see ha_high_thread_score.ha_mid_thread_score: specifies the number of working threads for medium-priority high-availability tasks such as migration. For more information about the tenant-level parameterha_mid_thread_score, see ha_mid_thread_score.ha_low_thread_score: specifies the number of working threads for low-priority high-availability tasks such as backup and backup cleanup. For more information about the tenant-level parameterha_low_thread_score, see ha_low_thread_score.
You can set the number of concurrent threads for writing files during backup by using the backup_concurrency parameter.
| Attribute | Description |
|---|---|
| Type | Int |
| Default value | 0 |
| Value range | [0, 100] |
| Effective upon OBServer node restart | No |
