Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-18015 JobHistoryServer Direct Memory Usage Exceeds the Threshold
Updated on 2024-09-23 GMT+08:00
View PDF
Share

ALM-18015 JobHistoryServer Direct Memory Usage Exceeds the Threshold

Description

The system checks the direct memory usage of the MapReduce service every 30 seconds. This alarm is generated when the direct memory usage of a JobHistoryServer instance exceeds the threshold (90% of the maximum memory).

The alarm is cleared when the direct memory usage is less than the threshold.

Attribute

Alarm ID

Alarm Severity

Automatically Cleared

18015

Major

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.

HostName

Specifies the host 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

If the available direct memory of the MapReduce service is insufficient, a memory overflow occurs and the service breaks down.

Possible Causes

The direct memory of the JobHistoryServer instance is overused or the direct memory is inappropriately allocated.

Procedure

Check the direct memory usage.

  1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > ALM-18015 JobHistoryServer Direct Memory Usage Exceeds the Threshold > Location to check the IP address of the instance for which the alarm is generated.
  2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Instance > JobHistoryServer (IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > Memory Usage Status of JobHistoryServer to check the direct memory usage.
  3. Check whether the used direct memory of JobHistoryServer reaches 90% of the maximum direct memory specified for JobHistoryServer by default.

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

  4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > MapReduce > Configurations > All Configurations > JobHistoryServer > System to check whether "-XX:MaxDirectMemorySize" exists in the GC_OPTS parameter.

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

  5. In the GC_OPTS parameter, delete "-XX:MaxDirectMemorySize".
  6. Save the configuration and restart the JobHistoryServer instance.

    During the restart of JobHistoryServer, the status query of tasks such as Hive is affected, and the query result may be inaccurate.

  7. Check whether the ALM-18009 Heap Memory Usage of JobHistoryServer Exceeds the Threshold exists.

    • If yes, handle the alarm by referring to ALM-18009 Heap Memory Usage of JobHistoryServer Exceeds the Threshold.
    • If no, go to 8.

  8. Check whether the alarm is cleared.

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

Collect fault information.

  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
  2. Select JobHistoryServer 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