OceanBase Database allows you to monitor the log archiving progress of the primary tenant in real time. If the archive checkpoint of the primary tenant is significantly different from the current time, log archiving of the primary tenant may be bottlenecked. You can adjust the log archiving concurrency of the primary tenant by modifying the tenant-level log_archive_concurrency parameter to accelerate the archiving speed of the primary tenant.
For more information about how to view the log archiving speed of the primary tenant, see View the archiving progress.
Procedure
Log on to the database as the administrator of the
systenant or the primary tenant.Set the
log_archive_concurrencyparameter to an appropriate value.The tenant-level
log_archive_concurrencyparameter specifies the total number of worker threads for log archiving. The modification of this parameter takes effect immediately without restarting the OBServer node. The default value of this parameter is1and the valid value ranges from [1 to 10]. If you set this parameter to a value greater than 10,10will be used instead. We recommend that you use the default value because more threads consume more memory.Notice
If the tenant is configured with 2 or 4 CPU cores, we recommend that you use the default value.
Execute the following statement to set the log archiving concurrency:
Execute the following statement in the primary tenant to adjust the log archiving speed of the primary tenant:
ALTER SYSTEM SET log_archive_concurrency = 10;Execute the following statement in the
systenant to adjust the log archiving speed of a specified tenant:ALTER SYSTEM SET log_archive_concurrency = 10 TENANT = oracle;Execute the following statement in the
systenant to adjust the log archiving speed of all tenants:ALTER SYSTEM SET log_archive_concurrency = 10 TENANT = ALL;
For more information about the
log_archive_concurrencyparameter, see log_archive_concurrency.