ALM-18002 NodeManager Heartbeat Lost (For MRS 2.x or Earlier)
Description
The system checks the number of lost NodeManager nodes every 30 seconds, and compares the number of lost nodes with the threshold. The Lost Nodes indicator has a default threshold. This alarm is generated when the value of the Lost Nodes indicator exceeds the threshold.
This alarm is cleared when the value of Lost Nodes is less than or equal to the threshold.
Attribute
Alarm ID |
Alarm Severity |
Auto Clear |
---|---|---|
18002 |
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. |
Trigger condition |
Generates an alarm when the actual indicator value exceeds the specified threshold. |
Impact on the System
- The lost NodeManager node cannot provide the Yarn service.
- The number of containers decreases, so the cluster performance deteriorates.
Possible Causes
- NodeManager is forcibly deleted without decommission.
- All NodeManager instances are stopped or the NodeManager process is faulty.
- The host where the NodeManager node resides is faulty.
- The network between the NodeManager and ResourceManager is disconnected or busy.
Procedure
- Collect fault information.
- On MRS Manager, choose System > Export Log.
- Contact the O&M engineers and send the collected logs.
Reference
None
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.