Help Center > > User Guide> FusionInsight Manager Operation Guide> Alarm Reference (Applicable to MRS 3.x)> ALM-14029 Number of Blocks in a Replica Exceeds the Threshold

ALM-14029 Number of Blocks in a Replica Exceeds the Threshold

Updated at: Mar 25, 2021 GMT+08:00

Description

The system checks the number of blocks in a single replica every four hours and compares the number with the threshold. There is a threshold for the number of blocks in a single replica. This alarm is generated when the actual number of blocks in a single replica exceeds the threshold.

This alarm is cleared when the number of blocks to be supplemented is less than the threshold.

Attribute

Alarm ID

Alarm Severity

Automatically Cleared

14029

Minor

Yes

Parameters

Name

Meaning

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.

NameServiceName

Specifies the NameService for which the alarm is generated.

Trigger condition

Specifies the threshold triggering the alarm. If the current indicator value exceeds this threshold, the alarm is generated.

Impact on the System

Replica data is prone to be lost when a node is faulty. Too many files of a single replica affect the security of the HDFS file system.

Possible Causes

  • The DataNode is faulty.
  • The disk is faulty.
  • Files are written to a single replica.

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. In the next detection period, check whether the alarm is cleared.

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

  3. Check whether files of a single replica have been written into the service.

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

  4. Log in to the HDFS client as user root. Run cd client installation directory to navigate to the client installation directory, and run source bigdata_env to configure the environment variables.
  5. If the cluster adopts the security mode, perform security authentication. Run the kinit hdfs command and enter the password as prompted. Obtain the password from the administrator.
  6. Run the following command on the client node to increase the number of replicas for a single replica file:

    hdfs dfs -setrep -w file replica number file name or file path

  7. In the next detection period, check whether the alarm is cleared.

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

Collect 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 the O&M personnel and send the collected logs.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

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