Help Center > > User Guide> Managing Active Clusters> Alarm Reference> ALM-18002 NodeManager Heartbeat Lost

ALM-18002 NodeManager Heartbeat Lost

Updated at: Feb 25, 2020 GMT+08:00


The system checks the number of lost NodeManager nodes every 30 seconds and compares the number with the threshold. This alarm is generated when the value of the Lost Nodes indicator exceeds the threshold and is cleared when the value is less than or equal to the threshold.


Alarm ID

Alarm Severity

Automatically Cleared








Specifies the service for which the alarm is generated.


Specifies the role for which the alarm is generated.


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.


  1. On MRS Manager, choose System > Export Log.
  2. Contact the O&M personnel and send the collected log information.

Related Information


Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel