Note
For V4.1.0, the scope of this parameter is adjusted to the tenant level.
Description
log_archive_concurrency specifies the concurrency level of log archiving.
Privilege requirements
Query the parameter
You can use the
SHOW PARAMETERSstatement or theGV$OB_PARAMETERSview to query this parameter for thesystenant and all user tenants.Modify the parameter
You can modify this parameter for the
systenant and user tenants.
Attributes
| Attribute | Description |
|---|---|
| Type | Int |
| Default value | 0, which indicates that the adaptive log archiving concurrency level of OceanBase Database is used.
NoteFor V4.2.0, the default value of this parameter is adjusted from 1 to 0. |
| Value range | [0, 100]
NoteFor V4.2.0, the value range of this parameter is adjusted from [1, 100] to [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
The number of archiving threads is calculated based on the adaptive value of max_cpu for the tenant:
- If
max_cpuis less than or equal to 8, the number of archiving threads is equal tomax_cpu. - If
max_cpuis greater than 8 and less than 32, the number of archiving threads ismax_cpu / 2, with a minimum of 8. - If
max_cpuis greater than or equal to 32, the number of archiving threads ismax_cpu / 4, with a minimum of 16.
Examples
Change the log archiving concurrency level of a MySQL user tenant.
obclient> ALTER SYSTEM SET log_archive_concurrency = 5 tenant = 'mysql';Change the log archiving concurrency level of a MySQL tenant.
obclient> ALTER SYSTEM SET log_archive_concurrency = 5;