Note
The effective scope of this parameter has been changed to the tenant level since OceanBase Database V4.1.0.
Description
log_archive_concurrency specifies the concurrency of log archiving.
Attributes
| Attribute | Description |
|---|---|
| Type | Integer |
| Default value | 0, which indicates that the concurrency of log archiving changes adaptively in OceanBase Database.
NoteThe default value of this parameter has been changed from |
| Value range | [0, 100]
NoteThe value range of this parameter has been changed from [1, 100] to [0, 100] since OceanBase Database V4.2.0. |
| Modifiable | Yes. You can use the ALTER SYSTEM SET statement to modify the parameter. |
| Effective upon OBServer node restart | No |
Considerations
The number of archiving worker threads is calculated based on the adaptive max_cpu value of the tenant as follows:
- If the
max_cpuvalue of the tenant ≤ 8, the number of archiving threads = themax_cpuvalue of the tenant. - If 8 < the
max_cpuvalue of the tenant < 32, the number of archiving threads = themax_cpuvalue of the tenant/2, with a minimum value of 8. - If the
max_cpu=value of the tenant > 32, the number of archiving threads = themax_cpuvalue of the tenant/4, with a minimum value of 16.
Examples
Modify the log archiving concurrency for a MySQL user tenant in the
systenant.obclient> ALTER SYSTEM SET log_archive_concurrency = 5 tenant = 'mysql';Modify the log archiving concurrency for a MySQL user tenant in the MySQL user tenant.
obclient> ALTER SYSTEM SET log_archive_concurrency = 5;