Help Center> GaussDB(DWS)> Management Guide> Monitoring and Alarms> Alarms> Alarm Handling> DWS_2000000023 Vacuum Full Operation That Holds A Table Lock Exceeds the Threshold

Updated on 2024-03-14 GMT+08:00

View PDF

DWS_2000000023 Vacuum Full Operation That Holds A Table Lock Exceeds the Threshold

Alarm Description

VACUUM FULL holds a level-8 lock on a table. If it holds the lock on a table for longer than 20 minutes (or another user-defined value), a major alarm is reported, indicating that the VACUUM FULL operation holds a lock for too long in the cluster. This major alarm is cleared when VACUUM FULL is complete.

Attributes

Alarm ID	Alarm Severity	Auto Cleared
DWS_2000000023	Important	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 VACUUM FULL operation [query_id] in the cluster takes more than 20 minutes.
Generated	Time when an alarm is generated.
Status	Status of the current alarm.

Impact on the System

Other operations cannot the table. As a result, workloads cannot be executed.

Possible Causes

There is a VACUUM FULL operation that holds a table lock for a long time in the cluster.

Handling Procedure

In the navigation pane of the monitoring panel, choose Monitoring > Queries. In the session list, set the search criteria to LIKE and search for the keyword vacuum full.
Check whether there is a table lock waiting for VACUUM FULL to complete by querying the locked object.
Check whether the VACUUM FULL operation needs to be handled.
1. Check whether VACUUM FULL is a system behavior and whether it affects system functions. If VACUUM FULL does not affect other service queries, wait until it is complete. The alarm will be automatically cleared.
2. If VACUUM FULL affects normal service execution, you can find and kill related sessions on the Real-Time Queries tab and re-execute VACUUM FULL later.