DWS_2000000020 SQL Probe of the Cluster Usage Exceeds the Threshold

Alarm Description

GaussDB(DWS) collects the execution status of the SQL probe on each node in the cluster every 30 seconds. If the execution duration of an SQL probe on a server in a cluster exceeds twice the threshold (or another user-defined value), a critical alarm is generated. If the execution duration of all SQL probes falls below the threshold, the critical alarm is cleared.

If the SQL probe duration remains higher than the alarm reporting threshold, the alarm is generated again in 24 hours(or another user-defined value).

Attributes

Alarm ID	Alarm Severity	Auto Cleared
DWS_2000000020	Critical	Yes

Alarm Parameters

Parameter	Description
Alarm Source	Name of the system for which the alarm is generated, for example, GaussDB(DWS).
Cluster Name	Cluster for which the alarm is generated.
Location Info	ID and name of the cluster for which the alarm is generated. Example: cluster_id: xxxx-xxxx-xxxx-xxxx,cluster_name: test_dws
Detail Information	Detailed information about the alarm, including the cluster and threshold information. Example: CloudService=DWS, resourceId: xxxx-xxxx-xxxx-xxxx, resourceIdName: test_dws, first_alarm_time: 2022-11-26 11:14:58; The test_dws cluster exceeds twice the SQL probe threshold. The number of SQL probes in the cluster exceeds the threshold:'select xxx from xxxx'.
Generated	Time when an alarm is generated.
Status	Status of the current alarm.

Impact on the System

The cluster performance deteriorates or the cluster is faulty.

Possible Causes

The service load of the cluster is high or the cluster is faulty. As a result, the execution of the SQL probe becomes slow.

Handling Procedure

In the navigation pane of the monitoring panel, choose Utilities > SQL Probes. Check SQL probe execution.
In the navigation pane, choose Monitoring > Performance Monitoring. Check the monitoring metrics such as the CPU usage, disk usage, and memory usage to determine whether the workloads are high or any metric is abnormal.
In the navigation pane, choose Monitoring > Real-Time Queries. Check whether there are queries or sessions that have been running for a long time and affect cluster running. You can terminate abnormal sessions or queries.