Help Center > > User Guide> FusionInsight Manager Operation Guide (Applicable to 3.x)> Alarm Reference (Applicable to MRS 3.x)> ALM-43007 Non-Heap Memory Usage of the JobHistory2x Process Exceeds the Threshold

ALM-43007 Non-Heap Memory Usage of the JobHistory2x Process Exceeds the Threshold

Updated at: Aug 17, 2021 GMT+08:00

Description

The system checks the JobHistory2x Process status every 30 seconds. The alarm is generated when the non-heap memory usage of a JobHistory2x Process exceeds the threshold (95% of the maximum memory).

Attribute

Alarm ID

Alarm Severity

Auto Clear

43007

Major

Yes

Parameters

Name

Meaning

Source

Specifies the cluster for which the alarm is generated.

ServiceName

Specifies the service name for which the alarm is generated.

RoleName

Specifies the role name for which the alarm is generated.

HostName

Specifies the object (host ID) 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 JobHistory2x Process non-heap memory is insufficient, a memory overflow occurs and the service breaks down.

Possible Causes

The non-heap memory of the JobHistory2x Process is overused or the non-heap memory is inappropriately allocated.

Procedure

Check non-heap memory usage.

  1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms and select the alarm whose ID is 43007. Check the RoleName in Location and confirm the IP address of HostName.
  2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance and click the JobHistory2x for which the alarm is generated to go to the Dashboard page. Click the drop-down menu in the Chart area and choose Customize > Memory > JobHistory2x Memory Usage Statistics from the drop-down list box in the upper right corner and click OK, Check whether the used non-heap memory of the JobHistory2x Process reaches the threshold(default value is 95%) of the maximum non-heap memory specified for JobHistory2x.

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

  3. On the FusionInsight Manager home page, choose Cluster > Name of the desired cluster > Services > Spark2x > Instance. Click JobHistory2x by which the alarm is reported to go to the Dashboard page, click the drop-down list in the upper right corner of the chart area, choose Customize > Memory > Statistics for the non-heap memory of the JobHistory2x Process, and click OK. Based on the alarm generation time, check the values of the used non-heap memory of the JobHistory2x process in the corresponding period and obtain the maximum value.
  4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Spark2x > Configurations, and click All Configurations. Choose JobHistory2x > Default. You can change the value of -XX:MaxMetaspaceSize in SPARK_DAEMON_JAVA_OPTS according to the following rules: Ratio of the JobHistory2x non-heap memory usage to the Threshold of JobHistory2x Non-Heap Memory Usage Statistics (JobHistory2x) in the alarm period.

    On the FusionInsight Manager home page, choose O&M > Alarm > Thresholds > Name of the desired cluster > Spark2x > Memory >JobHistory2x Non-Heap Memory Usage Statistics (JobHistory2x) to view Threshold.

  5. Restart all JobHistory2x instances.
  6. After 10 minutes, check whether the alarm is cleared.

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

Collect fault information.

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