ALM-17006 Oozie Direct Memory Usage Exceeds the Threshold

Alarm Description

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

Alarm Attributes

Alarm ID	Alarm Severity	Alarm Type	Service Type	Auto Cleared
17006	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 direct memory overflow may cause a service breakdown. After the service breaks down, the Oozie service cannot be used to schedule tasks.

Possible Causes

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

Handling Procedure

Check direct memory usage.

On the FusionInsight Manager portal, choose O&M > Alarm > Alarms > Oozie Direct 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 Direct Buffer Resource Percentage. Click OK.
Check whether the used direct memory of Oozie reaches the threshold (the default value is 80% of the maximum direct 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. Click All Configurations. Search GC_OPTS in the search box. Increase the value of -XX:MaxDirectMemorySize as required, and click Save. Click OK.

Suggestions on GC parameter settings for Oozie:

You are advised to set the value of -XX:MaxDirectMemorySize to 1/4 of the value of -Xmx. For example, if -Xmx is set to 4 GB, -XX:MaxDirectMemorySize is set to 1024 MB. If -Xmx is set to 2 GB, -XX:MaxDirectMemorySize is set to 512 MB. It is recommended that the value of -XX:MaxDirectMemorySize be greater than or equal 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 fault information.

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