Help Center/ MapReduce Service/ User Guide/ MRS Manager Operation Guide (Applicable to 2.x and Earlier Versions)/ Alarm Reference (Applicable to MRS 2.x and Earlier Versions)/ ALM-14009 Number of Faulty DataNodes Exceeds the Threshold (For MRS 2.x or Earlier)
Updated on 2024-04-11 GMT+08:00
View PDF

ALM-14009 Number of Faulty DataNodes Exceeds the Threshold (For MRS 2.x or Earlier)

Description

The system periodically checks the number of faulty DataNodes in the HDFS cluster every 30 seconds, and compares the number with the threshold. The number of faulty DataNodes has a default threshold. This alarm is generated when the number of faulty DataNodes in the HDFS cluster exceeds the threshold.

This alarm is cleared when the number of faulty DataNodes in the HDFS cluster is less than or equal to the threshold.

Attribute

Alarm ID

Alarm Severity

Auto Clear

14009

Major

Yes

Parameters

Parameter

Description

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

Generates an alarm when the actual indicator value exceeds the specified threshold.

Impact on the System

Faulty DataNodes cannot provide HDFS services.

Possible Causes

  • DataNodes are faulty or overloaded.
  • The network between the NameNode and the DataNode is disconnected or busy.
  • NameNodes are overloaded.

Procedure

  1. Check whether DataNodes are faulty.

    1. Use the client on the cluster node to run the hdfs dfsadmin -report command to check whether DataNodes are faulty.
      • If yes, go to 1.b.
      • If no, go to 2.a.
    2. On the MRS cluster details page, choose Components > HDFS > Instances to check whether the DataNode is stopped.
      • If yes, go to 1.c.
      • If no, go to 2.a.
    3. Select the DataNode instance, and choose More > Restart Instance to restart it. Wait 5 minutes and check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to 2.a.

  2. Check the status of the network between the NameNode and the DataNode.

    1. Log in to the service IP address of the node where the faulty DataNode is located, and run the ping IP address of the NameNode command to check whether the network between the DataNode and the NameNode is abnormal.
      • If yes, go to 2.b.
      • If no, go to 3.a.
    2. Rectify the network fault. Wait 5 minutes and check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to 3.a.

  3. Check whether the DataNode is overloaded.

    1. On the MRS cluster details page, click Alarms and check whether the alarm ALM-14008 HDFS DataNode Memory Usage Exceeds the Threshold exists.
      • If yes, go to 3.b.
      • If no, go to 4.a.
    2. Follow procedures in ALM-14008 HDFS DataNode Memory Usage Exceeds the Threshold (For MRS 2.x or Earlier) to handle the alarm and check whether the alarm is cleared.
      • If yes, go to 3.c.
      • If no, go to 4.a.
    3. Wait 5 minutes and check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to 4.a.

  4. Check whether the NameNode is overloaded.

    1. On the MRS cluster details page, click Alarms and check whether the alarm ALM-14007 HDFS NameNode Memory Usage Exceeds the Threshold exists.
      • If yes, go to 4.b.
      • If no, go to 5.
    2. Follow procedures in ALM-14007 HDFS NameNode Memory Usage Exceeds the Threshold (For MRS 2.x or Earlier) to handle the alarm and check whether the alarm is cleared.
      • If yes, go to 4.c.
      • If no, go to 5.
    3. Wait 5 minutes and check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to 5.

  5. Collect fault information.

    1. On MRS Manager, choose System > Export Log.
    2. Contact the O&M engineers and send the collected logs.

Reference

None