Note
This parameter is changed from a cluster-level parameter to a tenant-level parameter since OceanBase Database V4.1.0.
Description
log_archive_concurrency specifies the concurrency of log archiving.
Attributes
| Attribute | Description |
|---|---|
| Type | INT |
| Default value | 0, which indicates that the concurrency of log archiving changes adaptively in OceanBase Database.
NoteThe default value of this parameter is changed from 1 to 0 since OceanBase Database V4.2.0. |
| Value range | [0, 100]
NoteThe value range of this parameter is changed from [1,100] to [0,100] since OceanBase Database V4.2.0. |
| Modifiable | Yes. It can be modified using the ALTER SYSTEM SET statement. |
| Effective upon OBServer node restart | No |
Considerations
The number of archiving worker threads is calculated based on the tenant's max_cpu adaptive value as follows:
- If the tenant's
max_cpu≤ 8, the number of archiving threads =max_cpu. - If 8 < the tenant's
max_cpu< 32, the number of archiving threads = the tenant'smax_cpu/2, with a minimum value of 8. - If the tenant's
max_cpu> 32, the number of archiving threads = the tenant'smax_cpu/4, with a minimum value of 16.
Examples
The following example shows how to adjust the log archiving parallelism for the
systenant in the MySQL user tenant.obclient> ALTER SYSTEM SET log_archive_concurrency = 5 tenant = 'mysql';The following example shows how to adjust the log archiving parallelism for the MySQL tenant itself.
obclient> ALTER SYSTEM SET log_archive_concurrency = 5;