Overview
log_archive_concurrency specifies the concurrency level for log archiving.
Privilege requirements
Query parameters
Both the
systenant and all user tenants can query this parameter using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.Modify parameters
Both the
systenant and user tenants can modify this parameter.
Attributes
Attribute |
Description |
|---|---|
| Parameter type | Int |
| Default Value | 0 indicates using the adaptive log archiving parallelism of OceanBase AI Database. |
| Value range | [0,100] |
| Modifiable | Yes, you can use theALTER SYSTEM SETStatement modification. |
| Whether to restart the OBServer node for the change to take effect | No, the setting takes effect immediately. |
Usage instructions
The number of archiving worker threads is calculated based on the adaptive value of the tenant's max_cpu as follows:
- If
tenant max_cpu ≤ 8, thennumber_of_archiving_threads = max_cpu. - If
8 < tenant max_cpu < 32, thenNumber of archiving threads = tenant max_cpu / 2, with a minimum value of 8. - If
tenant_max_cpu >= 32, thenNumber of archiving threads = tenant_max_cpu / 4, with a minimum value of 16.
Configuration example
The sys tenant adjusts the log archiving parallelism for user tenants.
obclient> ALTER SYSTEM SET log_archive_concurrency = 5 tenant = 'mysql';Users can adjust the log archiving parallelism for their own tenants.
obclient> ALTER SYSTEM SET log_archive_concurrency = 5;
References
Log Archiving