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

ALM-17005 Oozie Non-Heap Memory Usage Exceeds the Threshold

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

Description

The system checks the non-heap memory usage of the Oozie service every 30 seconds. The alarm is generated when the non-heap memory usage of an Oozie instance exceeds the threshold (80% of the maximum memory). The alarm is cleared when the non-heap memory usage is less than the threshold.

Attribute

Alarm ID

Alarm Severity

Automatically Cleared

17005

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

The non-heap memory overflow may cause a service breakdown.

Possible Causes

The non-heap memory of the Oozie instance 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 > Oozie Non-Heap Memory Usage Exceeds the Threshold > Location. Check the IP address of the instance involved in this alarm.
  2. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Instance. Click the instance for which the alarm is generated to go to the page for the instance. Click the drop-down menu in the chart area and choose Customize > Memory > Oozie Non Heap Memory Resource Percentage. Click OK.
  3. Check whether the used non-heap memory of Oozie reaches the threshold (the default value is 80% of the maximum non-heap memory) specified for Oozie.

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

  4. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Configurations. Click All Configurations. Search GC_OPTS in the search box, check whether -XX: MaxPermSize exists. If yes, increase the value of -XX: MaxPermSize based on the site requirements. If no, manually add -XX: MaxPermSize and set the value to 1/8 of the value of -Xmx. Increase the value of -XX: MaxPermSize as required. And click Save. Click OK.

    Suggestions on GC parameter settings for Oozie:

    You are advised to set the value of -XX:MaxPermSize to 1/8 of the value of -Xmx. For example, if -Xmx is set to 2 GB, -XX:MaxPermSize is set to 256 MB. If -Xmx is set to 4 GB, -XX:MaxPermSize is set to 512 MB.

  5. Restart the affected services or instances and check whether the alarm is cleared.

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

Collect fault information.

  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
  2. Select Oozie in the required cluster from the Service drop-down list.
  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