ALM-17004 Oozie Heap Memory Usage Exceeds the Threshold

Alarm Description

The system checks the heap memory usage of the Oozie service every 60 seconds. The alarm is generated when the heap memory usage of a Metadata instance exceeds the threshold (95% of the maximum memory). The alarm is cleared when the heap memory usage is less than the threshold.

Alarm Attributes

Alarm ID	Alarm Severity	Alarm Type	Service Type	Auto Cleared
17004	Major	Quality of service	Oozie	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 threshold for triggering the alarm.

Impact on the System

The heap memory overflow may cause a service breakdown. After the service breaks down, the Oozie service cannot be used to schedule tasks.

Possible Causes

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

Handling Procedure

Check heap memory usage.

On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Oozie Heap Memory Usage Exceeds the Threshold > Location. Check the IP address of the instance involved in this alarm.
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 Heap Memory Resource Percentage. Click OK.
Check whether the used heap memory of Oozie reaches the threshold (the default value is 95% of the maximum heap memory) specified for Oozie.
- If yes, go to 4.
- If no, go to 6.
On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > Oozie > Configurations > All Configurations. Set Search GC_OPTS in the search box. Increase the value of -Xmx as required, and click Save > OK.

Suggestions on GC parameter settings for Oozie:

You are advised to set -Xms and -Xmx to the same value to prevent adverse impact on performance when JVM dynamically adjusts the heap memory size.
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.

On the FusionInsight Manager portal, choose O&M > Log > Download.
Select Oozie in the required cluster from the Service.
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 the O&M engineers and send the collected logs.