The exception handling feature displays the exceptions that have occurred or are occurring in the database cluster in the last 3 days. You can use this feature to quickly obtain the health status of the cluster and, when exceptions occur, perform root cause analysis to pinpoint the cause of the problem.
Prerequisites
You have completed one-click diagnostics and generated a diagnostic report. If not, please refer to Initiate one-click diagnostics.
Procedure
Log in to the OceanBase Cloud console.
In the left-side navigation pane, click Instances.
In the instance list, find the target instance, click the instance name, and go to the Overview page of the instance.
Click Diagnostics in the left-side navigation pane, and then select the Root Cause Diagnostics tab on the Diagnostics page.
In the Exceptions section, view the exception list of the current instance. By default, the system displays all exceptions in the last 3 days, including ongoing and restored exceptions.
Currently, the following exception types are supported: Node CPU Exception, Tenant CPU Exception, Tenant SQL Queue Waiting Time Exception, SQL High Error Rate Exception, Data Disk I/O Usage Exception, Tenant Active Session Count Exception, Tenant Disk I/O Latency Exception, Node Clog Disk I/O Usage High, Node Data Disk I/O Latency High, Node Data Disk Capacity Usage High.
Click Root Cause Analysis in the Actions column of a single exception.
If the cause of the exception is in the analysis graph, the system will highlight the cause in red and provide optimization suggestions.
Note
In the analysis graph, each node represents an analysis rule. When performing root cause analysis, the system traverses the graph to find the root cause node. The root cause node is highlighted in red, while the green node indicates that the rule does not hit the root cause.
If the cause of the exception is not in the analysis graph, the system will provide optimization suggestions in the Solution section.