Applicable scenarios
This article is applicable to the root cause analysis of transaction wait timeout errors, and is based on the analysis of OceanBase database internal table data and logs.
Currently, OceanBase database V4.0.0.0 and later versions are supported. 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 data, only current data is supported for analysis.
Can import environment variables
Variable name |
Is it required |
Data type |
Default value |
Description |
|---|---|---|---|---|
| error_msg | Yes | string | "" | Error message, optional Shared lock conflict, Lock wait timeout exceeded |
Usage example
The execution example of configuring the analysis scenario and configuring error information is as follows:
obdiag rca run --scene=transaction_wait_timeout --env error_msg="Shared lock conflict"