Description
The system checks the JobHistory process status every 30 seconds. The alarm is generated when the heap memory usage of the JobHistory process exceeds the threshold (90% of the maximum memory).
Attribute
Alarm ID
|
Alarm Severity
|
Automatically Cleared
|
43006
|
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 heap memory is insufficient, a memory overflow occurs and the service breaks down.
Possible Causes
The heap memory of the JobHistory process is overused or the heap memory is inappropriately allocated.
Procedure
- Check the heap memory usage.
- Go to the cluster details page and choose Alarms.
- Select the alarm whose Alarm ID is 43006 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 > Heap Memory Statistics of the JobHistory Process. Click OK to view the heap memory usage.
- Check whether the used heap memory of JobHistory reaches 90% of the maximum heap memory specified for JobHistory.
- If yes, go to 1.e.
- If no, go to 2.
- Choose Components > Spark > Service Configuration. Set Type to All and choose JobHistory > Default. Increase the value of SPARK_DAEMON_MEMORY as required.
- Click Save Configuration and select Restart the affected services or instances. Click OK.
- 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 .
- Contact technical support engineers for help. For details, see technical support.