ALM-17005 Oozie Non Heap Memory Usage Exceeds the Threshold

Alarm Description

The system checks the non heap memory usage of Oozie every 30 seconds. This alarm is reported if the non heap memory usage of Oozie exceeds the threshold (80%). This alarm is cleared if the non heap memory usage is lower than the threshold.

Alarm Attributes

Alarm ID	Alarm Severity	Alarm Type	Service Type	Auto Cleared
17005	Major	Quality of service	Oozie	Yes

Alarm Parameters

Type	Parameter	Description
Location Information	Source	Specifies the cluster for which the alarm was generated.
	ServiceName	Specifies the service for which the alarm was generated.
	RoleName	Specifies the role for which the alarm was generated.
	HostName	Specifies the host for which the alarm was generated.
Additional Information	Trigger Condition	Specifies the alarm triggering condition.

Impact on the System

The service may break down and the Oozie service cannot be used to schedule tasks.

Possible Causes

The non-heap memory of the Oozie instance is overused or the non-heap memory is inappropriately allocated.

Handling Procedure

Check non-heap memory usage.

On FusionInsight Manager, choose O&M > Alarm > Alarms > Oozie Non Heap Memory Usage Exceeds the Threshold. On the displayed page, check the location information of the alarm. Check the name of the instance host for which the alarm is generated.
On FusionInsight Manager, choose Cluster > Name of the target cluster > Services > Oozie and click the Instance tab. On the displayed page, select the role corresponding to the host name for which the alarm is generated and select Customize from the drop-down list in the upper right corner of the chart area. Choose Memory and select Oozie Non Heap Memory Resource Percentage. Click OK.
Check whether the non-heap memory used by Oozie reaches the threshold (80% of the maximum non-heap memory by default).
- If yes, go to 4.
- If no, go to 6.
On FusionInsight Manager, choose Cluster > Name of the target cluster > Services > Oozie and click the Configurations and then All Configurations. On the displayed page, search for the GC_OPTS parameter in the search box and check whether it contains -XX: MaxMetaspaceSize. If yes, increase the value of -XX: MaxMetaspaceSize based on the site requirements. If no, manually add -XX: MaxMetaspaceSize and set its value to 1/8 of the value of -Xmx. Click Save, and then click OK

JDK1.8 does not support the MaxPermSize parameter.

Suggestions on GC parameter settings for Oozie:

Set the value of -XX:MaxMetaspaceSize to 1/8 of the value of -Xmx. For example, if -Xmx is set to 2 GB, -XX:MaxMetaspaceSize is set to 256 MB. If -Xmx is set to 4 GB, -XX:MaxMetaspaceSize is set to 512 MB.
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 the fault information.

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