Help Center/ GaussDB(DWS)/ User Guide/ GaussDB(DWS) Cluster O&M/ Viewing GaussDB(DWS) Cluster Alarms/ Alarm Handling/ DWS_2000000033 GaussDB(DWS) Cluster Database Session Usage Exceeds the Threshold
Updated on 2025-01-06 GMT+08:00

DWS_2000000033 GaussDB(DWS) Cluster Database Session Usage Exceeds the Threshold

Alarm Description

The DMS alarm module will generate an alarm if the session usage of the cluster database goes over the threshold within a specific time frame and the suppression conditions are not met. The alarm will be resolved by the DMS alarm module once it detects that the session usage of the cluster database is below the threshold.

Alarm Attributes

Alarm ID

Alarm Category

Alarm Severity

Alarm Type

Service Type

Auto Cleared

DWS_2000000033

Management plane alarm

> 90 (Critical); > 80 (Major)

Service alarm

GaussDB(DWS)

Yes

Alarm Changes

Change Type

Change Version

Description

Reason for Change

New

8.2.1.230

New alarm

New alarm

Alarm Parameters

Type

Parameter

Description

Fault Location

Cluster name

Cluster for which the alarm is generated.

Tenant name

Name of the tenant to which the cluster belongs.

Alarm level

Severity of the alarm.

Additional Information

Resource ID

ID of the cluster for which the alarm is generated.

Resource name

Cluster for which the alarm is generated.

Database name

Name of the database for which the alarm is generated.

First_alarm_time

First occurrence event of an alarm, including the alarm threshold and current value.

Impact on the System

The number of available database connections is insufficient, affecting service execution.

Possible Causes

The maximum number of database connections is too small.

Procedure

  1. Log in to the GaussDB(DWS) console.
  2. On the Alarm page, view the alarms generated in the last seven days.
  3. Use gsql to connect to the cluster based on the alarm information. For details, see Using the CLI to Connect to a GaussDB(DWS) Cluster.
  4. Specify the maximum number of connections a user can have by using syntax CONNECTION LIMIT connlimit in the CREATE ROLE statement. If you need to modify this limit later, you can use the same syntax in the ALTER ROLE statement.

    1. Use PG_ROLES to check the maximum number of connections of a specified user.
      1
      2
      3
      4
      5
      SELECT ROLNAME,ROLCONNLIMIT FROM PG_ROLES WHERE ROLNAME='role1';
       rolname | rolconnlimit
      ---------+--------------
       role1   |           10
      (1 row)
      
    2. Change the maximum number of connections a user can have.
      1
      ALTER ROLE role1 connection limit 20;
      

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None