Note
This parameter is available starting with V4.6.3.
Overview
In shared storage mode, the LS checkpoint is used to persist the SYS_LS metadata of the sys tenant to shared storage.
sys_ckpt_thread_score specifies the score of a worker thread for an LS checkpoint at the cluster level. It controls the concurrency of tasks in the LS checkpoint queue and the upload concurrency of the bootstrap checkpoint during the initial cluster creation. If you set this parameter to 0, the default value 16 is used.
Privilege requirements
Query parameters
Both the
systenant and all user tenants can query this parameter using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.Modify parameters
Only the
systenant can modify this parameter. User tenants cannot modify it.
Attributes
Attribute |
Description |
|---|---|
| Parameter type | Int |
| Default Value | 16 |
| Value range | [0, 100] |
| Modifiable | Yes, you can use the following methods:ALTER SYSTEM SETStatement modification. |
| Whether to restart the OBServer node for the change to take effect | No, the setting takes effect immediately. |
Usage instructions
This parameter is a cluster-level parameter. Each OBServer node reads it via
GCONFand it is not configured separately for each tenant.Thread score indicates the concurrency quota for tasks in the
PRIO_LS_CKPTqueue within the DAG scheduler of each tenant. It does not mean that the entire cluster shares a single global thread pool. Therefore, this value does not indicate that all tenants in the cluster can only run a total of that many tasks.When creating a Bootstrap checkpoint DAG, the system creates Upload Tasks based on the effective thread score and sets a concurrency cap for a single DAG. The default value is
16. If explicitly configured as0, the default score16is used. Periodic NORMAL checkpoints always create exactly one Upload Task.The Bootstrap checkpoint DAG is created only during the initial cluster creation. After the cluster is created, dynamically modifying this parameter will only refresh the task concurrency quota for the
PRIO_LS_CKPTqueue in the DAG scheduler of each tenant, without recreating the Bootstrap checkpoint DAG.When creating a cluster for the first time, if you need to explicitly specify the upload concurrency for the Bootstrap checkpoint, configure the same
sys_ckpt_thread_scorevalue in the-ostartup parameter on each OBServer node. The-oparameter applies only to the currently starting OBServer process. If not explicitly specified, the default value16is used.Before adjusting this parameter, evaluate the number of tenants, CPU, memory, DAG queue, and object storage pressure on each OBServer node. It is recommended to use the default value
16first and gradually increase it only when there is a significant upload bottleneck for the first Bootstrap checkpoint and resources are sufficient.
Configuration example
When creating a cluster for the first time, specify
sys_ckpt_thread_scoreusing the OBServer startup parameter../bin/observer \ -n ob1.shuili.wh \ -c 1 \ -P 1424 \ -p 1459 \ -z z1 \ -d /data/1/ob1.z1.obs0/store \ -m shared_storage \ -o "sys_ckpt_thread_score=32,enable_logservice=True" \ -i eth0The
-ooption is followed by a configuration string in thekey=valueformat, separated by commas. If other startup configurations are already present, you should combine thesys_ckpt_thread_score=32configuration into the same-ooption; do not add a second-oseparately.After the cluster is created, dynamically modify this parameter.
ALTER SYSTEM SET sys_ckpt_thread_score = 32;View the current configuration.
SHOW PARAMETERS LIKE 'sys_ckpt_thread_score';