On this page

Show all

Help Center/ MapReduce Service/ User Guide (Ankara Region)/ Alarm Reference/ ALM-27005 Database Connection Usage Exceeds the Threshold

ALM-27005 Database Connection Usage Exceeds the Threshold

Updated on 2024-11-29 GMT+08:00

View PDF

Alarm Description

The system checks the database connection usage of the DBServer node every 30 seconds and compares the actual database connection usage with the threshold. This alarm is generated when the database connection usage exceeds the threshold for five consecutive times (configurable, five by default).

The trigger count is configurable. When the value is 1 and the data connections are no more than the threshold, the alarm is cleared. When the trigger count is greater than 1 and the data connections are no more than 90% of the threshold, the alarm is cleared.

Alarm Attributes

Alarm ID	Alarm Severity	Alarm Type	Service Type	Auto Cleared
27005	Critical (default threshold: 95%) Major (The default threshold: 90%)	Quality of service	FusionInsight Manager	Yes

Alarm ID

Alarm Severity

Alarm Type

Service Type

Auto Cleared

27005

Critical (default threshold: 95%)

Major (The default threshold: 90%)

Quality of service

FusionInsight Manager

Yes

Alarm Parameters

Type	Parameter	Description
Location Information	Source	Specifies the cluster for which the alarm is generated.
	ServiceName	Specifies the service for which the alarm is generated.
	RoleName	Specifies the role for which the alarm is generated.
	HostName	Specifies the host for which the alarm is generated.
Additional Information	Trigger condition	Specifies the alarm triggering condition.

Impact on the System

Upper-layer services may fail to connect to the DBService database, affecting services.

Possible Causes

There are too many database connections in use.
The maximum number of database connections is set improperly.
The alarm threshold or alarm trigger count is improperly configured.

Handling Procedure

Check whether there are too many database connections in use.

On FusionInsight Manager, click DBService in the service list on the left. The DBService monitoring page is displayed.
View the number of connections used by the database user, as shown in Figure 1. You can reduce the number of connections based on service requirements.

Figure 1 Connections used by the database user
Wait 2 minutes and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 4.

Check whether the maximum number of database connections is set properly.

Log in to FusionInsight Manager, choose Cluster > Name of the desired cluster > Service > DBService, click Configuration and then All Configurations. Increase the maximum number of database connections allowed based on service requirements. After the modification, click Save. On the page that is displayed, click OK.

Figure 2 Setting maximum database connections
After changing the maximum number of database connections, restart DBService (do not restart its upper-layer services).

Procedure: Log in to FusionInsight Manager, choose Cluster > Name of the desired cluster > Service > DBService. On the displayed page, click More > Restart Service in the upper right corner, enter the password of the current login user, and click OK. Do not select Restart upper-layer services. Click OK.
Wait 2 minutes and check whether the alarm is automatically cleared.
- If yes, no further action is required.
- If no, go to 7.

Check whether the alarm threshold or alarm trigger count is properly configured.

Log in to FusionInsight Manager and change the alarm threshold and alarm smoothing times based on the number of database connections. Click O&M and choose Alarm > Thresholds in the navigation pane on the left. On the displayed page, click the name of the desired cluster > DBService > Database > Database Connection Usage (DBServer). Click the pencil icon next to Trigger Count to change the value.

NOTE:

If the value of Trigger Count exceeds the threshold, the alarm is generated.

Figure 3 Setting the alarm trigger count

Click O&M, and choose Alarm > Thresholds in the navigation pane on the left. On the displayed page, click the name of the desired cluster > DBService > Database > Database Connection Usage (DBServer) in the list on the left. Click Modify in the Operation column. Modify the rule and click OK. The modification takes effect immediately.

Figure 4 Configuring the alarm threshold
Wait 2 minutes and check whether the alarm is automatically cleared.
- If yes, no further action is required.
- If no, go to 9.

Collect fault information.

On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
Expand the Service drop-down list, and select DBService for the target cluster.
Specify Hosts for collecting logs, which is optional. By default, all hosts are selected.
Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
Contact O&M engineers and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.

Parent topic: Alarm Reference

Previous topic: ALM-27004 Data Inconsistency Between Active and Standby DBServices

Next topic: ALM-27006 Data Directory Disk Usage Exceeds the Threshold

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot