Overview
shared_storage_data_check_thread_score specifies the thread score for the data existence inspection DAG in shared storage. A value of 0 indicates using the built-in default thread score, which is currently 3. A value of 1 to 100 indicates explicitly specifying the scheduling thread score for the inspection task.
Privilege requirements
Query parameters
Both the
systenant and all user tenants can query this parameter using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.Modify parameters
Both the
systenant and user tenants can modify this parameter.
Attributes
Attribute |
Description |
|---|---|
| Parameter type | Int |
| Default Value | 0, corresponding to the built-in default thread score of 3. |
| Value range | [0, 100] |
| Modifiable | Yes, you can use theALTER 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 used to update the scheduling thread score of
DAG_PRIO_SS_DATA_CHECKand control the number of tasks that can run in parallel under this priority. The maximum number of parallel workers generated during the Expected collection phase is derived from the effective scheduling quota ofDAG_PRIO_SS_DATA_CHECK. Therefore, this parameter also affects the parallel read and parsing speed of shared metadata, the generation speed of the Expected macroblock set, the concurrent resource usage for temporary file writing and out-of-order merging, the overall execution efficiency of object storage LIST checking, and the worker thread resource allocation for the tenant's DAG scheduler. - The default value is 0, which means the built-in default thread score is used. The current built-in default value is 3. When set to a value between 1 and 100, the explicitly specified thread score in the configuration is used. A higher value indicates a higher concurrency quota available for that priority. The actual concurrency is still subject to the total number of tenant threads, competition from other DAG tasks, and the number of currently executable tasks.
- A smaller value reduces the concurrent pressure of inspections on CPU, memory, shared meta, and object storage. A larger value improves the inspection speed for large tenants but may increase temporary file I/O and object storage LIST pressure.
- This parameter specifies the score for scheduling threads, not the fixed number of independent OS threads created for inspection. Lowering the thread score does not forcibly terminate running tasks; it only affects subsequent task generation and scheduling. Setting it to 0 does not disable inspection.
Configuration example
Use the built-in default thread score. The current valid value is 3.
obclient> ALTER SYSTEM SET shared_storage_data_check_thread_score = 0;Explicitly set the thread score to 3.
obclient> ALTER SYSTEM SET shared_storage_data_check_thread_score = 3;Reduce the inspection concurrency by setting the thread score to 1.
obclient> ALTER SYSTEM SET shared_storage_data_check_thread_score = 1;Increase the inspection concurrency for the root tenant by setting the thread score to 6.
obclient> ALTER SYSTEM SET shared_storage_data_check_thread_score = 6;