ALM-46005 MOTService Database Connection Usage Exceeds the Threshold

Alarm Description

The system checks the database connection usage of the MOTServer 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 (90% by default) for five consecutive times (5 by default).

• If Trigger Count is 1, this alarm is cleared when the database connection usage is less than or equal to the threshold.
• If Trigger Count is greater than 1, this alarm is cleared when the database connection usage is less than or equal to 90% of the threshold.

Alarm Attributes

Alarm Parameters

Impact on the System

If there are too many MOTService database connections, upper-layer services may fail to connect to the MOTService database.

Possible Causes

• There are too many database connections.
• 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.

1. On FusionInsight Manager, choose Cluster > Services > MOTService. The Dashboard page is displayed.
2. In the Chart area, view the Connections Used by MOT User chart to check whether there are too many database connections.
   • If yes, go to 3.
   • If no, go to 5.

3. Reduce the number of database connections based on the service scenario, that is, close some connections.
4. Wait 2 minutes and check whether the alarm is automatically cleared.
   • If yes, no further action is required.
   • If no, go to 5.

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

5. On FusionInsight Manager, choose Cluster > Services > MOTService > Configuration > All Configurations and check whether the maximum number of database connections motservice.database.max.connections meets service requirements.
   • If yes, go to 9.
   • If no, go to 6.

6. Increase the maximum number of database connections based on site requirements. The maximum number of database connections must be greater than the number of service data connections.
7. On the Dashboard page, click More and select Restart Service. Enter the user password and click OK to restart the MOTService service.
8. Wait 2 minutes and check whether the alarm is automatically cleared.
   • If yes, no further action is required.
   • If no, go to 9.

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

9. Log in to FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, choose MOTService > Database > MOT Connections Usage (MOTServer), and check whether the alarm trigger count and alarm threshold are set properly.
   • If yes, go to 12.
   • If no, go to 10.

10. Change the trigger count and alarm threshold based on the actual number of of database connections, and apply the changes.
11. Wait 2 minutes and check whether the alarm is automatically cleared.
    • If yes, no further action is required.
    • If no, go to 12.

Collect fault information.

12. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
13. Expand the Service drop-down list and select MOTService.
14. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs.
15. Click the edit icon 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.
16. Contact O&M personnel/Technical support and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None