Help Center/ MapReduce Service/ User Guide (Ankara Region)/ Alarm Reference/ ALM-43006 Heap Memory Usage of the JobHistory Process Exceeds the Threshold
Updated on 2024-11-29 GMT+08:00

ALM-43006 Heap Memory Usage of the JobHistory Process Exceeds the Threshold

Alarm Description

The system checks the heap memory usage of the JobHistory process every 30 seconds. A major alarm is reported when the heap memory usage is greater than 95% of the maximum memory. A minor alarm is reported when the usage is greater than 85% and less than 95% of the maximum memory.

Alarm Attributes

Alarm ID

Alarm Severity

Alarm Type

Service Type

Auto Cleared

43006

Major (default threshold: 95% of the maximum memory)

Major (default threshold: 85% of the maximum memory)

Quality of service

Spark

Yes

Alarm Parameters

Type

Parameter

Description

Location Information

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.

Additional Information

Trigger Condition

Specifies the alarm triggering condition.

Impact on the System

If the direct memory usage of the JobHistory process is too high, the performance deteriorates, and the process even becomes unavailable due to memory overflow. When it is unavailable, execution records of Spark tasks cannot be queried.

Possible Causes

The heap memory of the JobHistory process is overused or the heap memory is inappropriately allocated.

Handling Procedure

Check the heap memory usage.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms and select the alarm whose ID is 43006. Check the role name and the IP address of the host where the alarm is generated in Location.
  2. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark > Instance. Click the JobHistory that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > JobHistory Memory Usage Statistics > OK. Check whether the heap memory used by the process reaches the maximum heap memory threshold (95% by default).

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

  3. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark > Instance. Click the JobHistory that reported the alarm to go to the Dashboard page. Click the drop-down list in the upper right corner of the chart area, and choose Customize > Memory > Heap Memory Statistics for the heap memory of the JobHistory process > OK. Based on the alarm generation time, check the values of the used heap memory of the process in the corresponding period and obtain the maximum value.
  4. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Spark > Configurations, click All Configurations, and select JobHistory > Default. The default value of SPARK_DAEMON_MEMORY is 4G. You can change the value based on the ratio of the maximum JobHistory heap memory usage to the threshold specified by JobHistoryHeap Memory Usage Statistics (JobHistory) in the alarm period. If the alarm persists after the parameter value is changed, increase the value by 0.5 times. If the alarm is generated frequently, increase the value by one time.

    On FusionInsight Manager, you can choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark > Memory > Spark Heap Memory Usage Statistics (Spark) to view the threshold.

  5. Restart all JobHistory instances.
  6. Check whether the alarm is cleared 10 minutes later.

    • 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 Spark for the target cluster.
  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 engineers and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.