Help Center > > User Guide> FusionInsight Manager Operation Guide (Applicable to 3.x)> Alarm Reference (Applicable to MRS 3.x)> ALM-14028 Number of Blocks to Be Supplemented Exceeds the Threshold

ALM-14028 Number of Blocks to Be Supplemented Exceeds the Threshold

Updated at: Sep 02, 2021 GMT+08:00

Description

The system checks the number of blocks to be supplemented every 30 seconds and compares the number with the threshold. The number of blocks to be supplemented has a default threshold. This alarm is generated when the number of blocks to be supplemented exceeds the threshold.

You can change the threshold specified by Blocks Under Replicated (NameNode) by choosing O&M > Alarm > Thresholds > Name of the desired cluster > HDFS > File and Block.

If Trigger Count is set to 1 and the number of blocks to be supplemented is less than or equal to the threshold, this alarm is cleared. If Trigger Count is greater than 1 and the number of blocks to be supplemented is less than or equal to 90% of the threshold, this alarm is cleared.

Attribute

Alarm ID

Alarm Severity

Auto Clear

14028

Minor

Yes

Parameters

Name

Meaning

Source

Specifies the cluster for which the alarm is generated.

ServiceName

Specifies the name of the service for which the alarm is generated.

RoleName

Specifies the name of the role for which the alarm is generated.

HostName

Specifies the host for which the alarm is generated.

NameServiceName

Specifies the NameService for which the alarm is generated.

Trigger condition

Specifies the threshold for triggering the alarm.

Impact on the System

Data stored in HDFS is lost. HDFS may enter the security mode and cannot provide write services. Lost block data cannot be restored.

Possible Causes

  • The DataNode instance is abnormal.
  • Data is deleted.
  • The number of replicas written into the file is greater than the number of DataNodes.

Procedure

  1. On FusionInsight Manager portal, choose O&M > Alarm > Alarms and check whether ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold is generated.

    • If yes, go to 2.
    • If no, go to 3.

  2. Rectify the fault according to the handling procedure of ALM-14003 Number of Lost HDFS Blocks Exceeds the Threshold. Five minutes later, check whether the alarm is cleared.

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

  1. Log in to the HDFS client as user root. The user password is defined by the user before the installation. Contact the system administrator to obtain the password. Run the following commands:

    • Security mode:

      cd Client installation directory

      source bigdata_env

      kinit hdfs

    • Normal mode:

      su - omm

      cd Client installation directory

      source bigdata_env

  2. Run the hdfs fsck / >> fsck.log command to obtain the status of the current cluster.
  3. Run the following command to count the number (M) of blocks to be replicated:

    cat fsck.log | grep "Under-replicated"

  4. Run the following command to count the number (N) of blocks to be replicated in the /tmp/hadoop-yarn/staging/ directory:

    cat fsck.log | grep "Under replicated" | grep "/tmp/hadoop-yarn/staging/" | wc -l

    /tmp/hadoop-yarn/staging/ is the default directory. If the directory is modified, obtain it from the configuration item yarn.app.mapreduce.am.staging-dir in the mapred-site.xml file.

  5. Check whether the percentage of N is greater than 50% (N/M > 50%).

    • If yes, go to 8.
    • If no, go to 9.

  6. Run the following command to reconfigure the number of file replicas in the directory (set the number of file replicas to the number of DataNodes or the default number of file replicas):

    hdfs dfs -setrep -w Number of file replicas/tmp/hadoop-yarn/staging/

    To obtain the default number of file replicas:

    Log in to FusionInsight Manager, choose Cluster > Services > HDFS > Configurations > All Configurations, and search for the dfs.replication parameter. The value of this parameter is the default number of file replicas.

    Wait for 5 minutes and check whether the alarm is cleared.

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

Collect the fault information.

  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
  2. Select HDFS in the required cluster from the Service.
  3. 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.
  4. Contact O&M personnel and send the collected logs.

Alarm Clearing

After the fault that triggers the alarm is rectified, the alarm is automatically cleared.

Related Information

None

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel