Support Questions

Find answers, ask questions, and share your expertise

Nodemanager service is failing on new host of HDP cluster after adding to the cluster.

avatar
Contributor

Getting the following message:

ERROR nodemanager.NodeStatusUpdaterImpl (NodeStatusUpdaterImpl.java:serviceStart(229)) - Unexpected error starting NodeStatusUpdater org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Recieved SHUTDOWN signal from Resourcemanager, Registration of NodeManager failed, Message from ResourceManager: Disallowed NodeManager from hostxxx.corpintra.net, Sending SHUTDOWN signal to the NodeManager.

1 ACCEPTED SOLUTION

avatar
Expert Contributor

@Narasimha K Have you added this host to exclude list?

  1. Check /etc/hadoop/conf/yarn.exclude . If this host exists in this file remove it
  2. Execute yarn rmadmin -refreshNodes so YARN re-reads this configuration file

View solution in original post

4 REPLIES 4

avatar
Expert Contributor

@Narasimha K Have you added this host to exclude list?

  1. Check /etc/hadoop/conf/yarn.exclude . If this host exists in this file remove it
  2. Execute yarn rmadmin -refreshNodes so YARN re-reads this configuration file

avatar
Contributor

The issue was resolved once the steps.

avatar
New Contributor

Thanks the issue resolved after following the above steps. After re-adding the node, which was decommissioned earlier, it was crashing to start. YARN>Summary>NodeManagers Status was also showing 1 node with decommissioned status but will the cleanup not happen during the install process?

,

Thanks, Issue resolved after completing the below steps. The newly added host/nodemanager was crashing and the YARN>Summary>NodeManagers Status was showing 1 node in decommissioned status

  1. Check /etc/hadoop/conf/yarn.exclude . If this host exists in this file remove it
  2. Execute yarn rmadmin -refreshNodes so YARN re-reads this configuration file

when you re-add the host again, should not the file get updated automatically?

avatar
Contributor

After decommissioning, recommission the nodemanager and then start it again.