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 ID |
Alarm Severity |
Automatically Cleared |
---|---|---|
17006 |
Major |
Yes |
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. |
The direct memory overflow may cause a service breakdown.
The direct memory of the Oozie instance is overused or the direct memory is inappropriately allocated.
Check direct memory usage.
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.
Collect fault information.
After the fault is rectified, the system automatically clears this alarm.
None