Applicable scenarios
This article is suitable for root cause analysis of partition split scheduling errors, based on the analysis of OceanBase database internal table data and logs, to help locate the cause of partition split scheduling failure.
When using obdiag, you need to configure the cluster information in the ~/.obdiag/config.yml file according to your choice, or configure the cluster information through the --config option in the command.
Attention
Due to the timeliness of internal table data, only current data is supported for analysis.
Can import environment variables
Variable name |
Is it required |
Data type |
Default value |
Description |
|---|---|---|---|---|
| tenant_id | No | string | "" | Specifies the tenant ID to be analyzed. |
| table_id | No | string | "" | Specifies the table ID to be analyzed. |
Usage example
- Configure analysis scenarios, executed by default
obdiag rca run --scene=split_schedule_error
```* Configure the analysis scenario and specify the tenant ID
```shell
obdiag rca run --scene=split_schedule_error --env tenant_id=1001
```* Configure the analysis scenario and specify the table ID
```shell
obdiag rca run --scene=split_schedule_error --env table_id=500001
Analyze content
This scenario analyzes the following:
- Split task status: Check the execution status of the partition split task.
- Scheduler Status: Analyze the running status of the split scheduler.
- Causes of splitting blocking: Analyze the reasons that may cause splitting scheduling blocking.
- Log Analysis: Analyze split-related error messages in OceanBase cluster logs.
Output results
After the analysis is completed, a diagnostic report will be generated, which includes:
- Root cause analysis results of split scheduling errors
- Problem location information
- Fix suggestions
Common reasons
Common causes of partition split scheduling errors include:
- The split target partition already exists.
- Insufficient resources cause splitting to fail.
- An exception occurred during the splitting process.
- The scheduler status is abnormal.
Solution suggestions
- Check status and error messages of split tasks.
- Confirm whether resources (memory, disk, etc.) are sufficient.
- If you find that the scheduler is abnormal, you can try to restart related services.
- If it is confirmed to be a bug, please upgrade to the fixed version or contact technical support.