ALM-43008 Direct Memory Usage of the JobHistory Process Exceeds the Threshold

Alarm Description

The system checks the direct memory usage of the JobHistory process every 30 seconds. A major alarm is reported when the direct 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 Parameters

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 direct memory of the JobHistory process is overused or the direct memory is inappropriately allocated.

Handling Procedure

Check the direct memory usage.

1. On FusionInsight Manager, choose O&M > Alarm > Alarms and select the alarm whose ID is 43008. 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 direct memory used by the process reaches the maximum direct 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 > Direct Memory of JobHistory > OK. Based on the alarm generation time, check the values of the used direct 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 > All Configurations > JobHistory > Default. You can change the value of XX:MaxDirectMemorySize (the default value is 512 MB) in the SPARK_DAEMON_JAVA_OPTS parameter based on the ratio of the maximum direct memory used by the JobHistory process to the threshold specified by JobHistory Direct 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, double the rate. It is recommended that the rate be less than or equal to the value of the SPARK_DAEMON_MEMORY parameter.
   

   On FusionInsight Manager, you can choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark > Memory > JobHistory Non-Heap Memory Usage Statistics (JobHistory) 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.

7. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
8. Expand the Service drop-down list, and select Spark for the target cluster.
9. 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.
10. Contact O&M engineers and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.