Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-25007 Number of SlapdServer Connections Exceeds the Threshold
Updated on 2024-09-23 GMT+08:00
View PDF
Share

ALM-25007 Number of SlapdServer Connections Exceeds the Threshold

Alarm Description

The system checks the number of process connections on the SlapdServer node every 30 seconds and compares the actual number with the threshold. This alarm is generated when the number of process connections exceeds the threshold (1000 by default) for multiple times (5 by default).

Its Trigger Count is configurable. If Trigger Count is set to 1, this alarm is cleared when the number of process connections is less than or equal to the threshold. If Trigger Count is greater than 1, this alarm is cleared when the number of process connections is less than or equal to 90% of the threshold.

Alarm Attributes

Alarm ID

Alarm Severity

Auto Cleared

25007

Major

Yes

Alarm Parameters

Parameter

Description

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.

Trigger Condition

Specifies the threshold for triggering the alarm.

Impact on the System

SlapdServer may respond slowly or become unavailable. Kerberos authentication times out or OS user caches cannot be synchronized. Component services are faulty.

Possible Causes

  • There are too many SlapdServer connections.
  • The alarm threshold or alarm trigger count is improperly configured.

Handling Procedure

Check whether there are too many SlapdServer process connections.

  1. Log in to FusionInsight Manager and choose Cluster > Services > LdapServer.
  2. On the LdapServer dashboard page, observe the SlapdServer process connections and decrease the connections based on service requirements.

    Figure 1 SlapdServer process connections

  3. Wait about 2 minutes and check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 4.

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

  1. On FusionInsight Manager, choose O&M > Alarm > Thresholds, click the name of the desired cluster, choose LdapServer > Other > SlapdServer Service Connections, and check whether the alarm trigger count and alarm threshold are set properly.

    • If yes, go to 7.
    • If no, go to 5.

  2. Change the trigger count and alarm threshold based on the actual number of process connections, and apply the changes.
  3. Wait 2 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, go to 7.

Collect fault information.

  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
  2. Expand the Service drop-down list, and select LdapServer for the target cluster.
  3. Specify Hosts for collecting logs, which is optional. By default, all hosts are selected.
  4. 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.
  5. Contact O&M personnel and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.