ALM-43008 Direct Memory Usage of the JobHistory Process Exceeds the Threshold¶
Description¶
The system checks the JobHistory process status every 30 seconds. The alarm is generated when the direct memory usage of the JobHistory process exceeds the threshold (90% of the maximum memory).
Attribute¶
Alarm ID | Alarm Severity | Automatically Cleared |
|---|---|---|
43008 | Major | Yes |
Parameters¶
Parameter | Description |
|---|---|
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. |
Impact on the System¶
If the available JobHistory process direct memory is insufficient, a memory overflow occurs and the service breaks down.
Possible Causes¶
The direct memory of the JobHistory process is overused or the direct memory is inappropriately allocated.
Procedure¶
Check the direct memory usage.
Go to the cluster details page and choose Alarms.
Select the alarm whose Alarm ID is 43008 and view the IP address and role name of the instance in Location.
Choose Components > Spark > Instance > JobHistory (IP address of the instance for which the alarm is generated) > Customize > Direct Memory Statistics of the JobHistory Process. Click OK to view the direct memory usage.
Check whether the direct memory usage of the JobHistory process has reached the threshold (90% of the maximum direct memory).
Choose Components > Spark > Service Configuration. Set Type to All and choose JobHistory > Default. Increase the value of -XX:MaxDirectMemorySize in SPARK_DAEMON_JAVA_OPTS as required.
Check whether the alarm is cleared.
If yes, no further action is required.
If no, go to 2.
Collect fault information.
On MRS Manager, choose System > Export Log.
Contact technical support engineers for help. For details, see technical support.
Reference¶
None