| Potential Root Cause: | Troubleshooting Steps: | ||||||||
| Hostname in Exclude File or | • Verify the contents of the files referenced in the | ||||||||
| Doesn't Exists in Include File | yarn.resourcemanager.nodes.excludepath | ||||||||
| property or the | |||||||||
| yarn.resourcemanager.nodes.include-path | |||||||||
| property. | |||||||||
| • Verify that the host for this Node Manager is not | |||||||||
| being decommissioned. | |||||||||
Resolution Steps: | |||||||||
| • If hostname for the Node Manager is in the file, and it | |||||||||
| is not meant for decommissioning, remove it. | |||||||||
Information to Collect: | |||||||||
| • Files that are pointed to by the | |||||||||
| yarn.resourcemanager.nodes.exclude-path | |||||||||
| or yarn.resourcemanager.nodes.includepath | |||||||||
| properties. | |||||||||
| Potential Root Cause: Node | Troubleshooting Steps: | ||||||||
| was Decommissioned and/or | • This is a problem with HDFS. Refer to the HDFS | ||||||||
| Reinserted into the Cluster | Troubleshooting Guide. | ||||||||
| Potential Root Cause: Resource | Troubleshooting Steps: | ||||||||
| Manager is Refusing the | • Follow the steps (described previously) to ensure that | ||||||||
| Connection | the NameNode has started and is accepting requests. | ||||||||
| Resolution Steps: | |||||||||
| • Ensure that the DataNode is not in the "exclude" list. | |||||||||
| • Ensure that the DataNode host is in the "include" list. | |||||||||
| Information to Collect: | |||||||||
| • NameNode slaves file. | |||||||||
| • NameNode hosts.deny file (or the file specified as | |||||||||
| the blacklist in HDFS configuration). | |||||||||
| • NameNode hosts.allow file (or the file specified as | |||||||||
| the whitelist in HDFS configuration). | |||||||||
| • HDFS Configuration. | |||||||||
| Potential Root Cause: | Troubleshooting Steps: | ||||||||
| NameNode is Refusing the | • Follow the steps (described previously) to ensure that | ||||||||
| Connection | the NameNode has started and is accepting requests. | ||||||||
| Resolution Steps: | |||||||||
| • Ensure that the DataNode is not in the "exclude" list. | |||||||||
| Information to Collect: | |||||||||
| • NameNode slaves file. | |||||||||
| • NameNode hosts.deny file (or the file specified as | |||||||||
| the blacklist in HDFS configuration). | |||||||||
| • NameNode hosts.allow file (or the file specified as | |||||||||
| the whitelist in HDFS configuration). | |||||||||
| • HDFS Configuration. | |||||||||
Monday, February 6, 2017
Node Manager Denied Communication with Resource Manager -Server Side Issue
Subscribe to:
Post Comments (Atom)
Kafka Architecture
Apache Kafka is a distributed publish-subscribe messaging system and a robust queue that can handle a high volume of data and enables you t...
-
HDFS is core part of any Hadoop deployment and in order to ensure that data is protected in Hadoop platform, security needs to be baked int... -
1. Working with data delivery teams to setup new Hadoop users. This job includes setting up Linux users, setting up Kerberos principals an...
-
This blog provides instructions on setting up the ResourceManager (RM) High Availability (HA) feature in a HDFS cluster. The Active and ...
No comments:
Post a Comment