[ https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687948#comment-13687948 ]
Hudson commented on YARN-848: ----------------------------- Integrated in Hadoop-Hdfs-trunk #1435 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1435/]) YARN-848. Fix NodeManager to register with RM using the fully qualified hostname. Contributed by Hitesh Shah. (Revision 1494385) Result = FAILURE sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1494385 Files : * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/ContainerManagerImpl.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/TestContainerManager.java > Nodemanager does not register with RM using the fully qualified hostname > ------------------------------------------------------------------------ > > Key: YARN-848 > URL: https://issues.apache.org/jira/browse/YARN-848 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Hitesh Shah > Assignee: Hitesh Shah > Fix For: 2.1.0-beta > > Attachments: YARN-848.1.patch, YARN-848.3.patch > > > If the hostname is misconfigured to not be fully qualified ( i.e. hostname > returns foo and hostname -f returns foo.bar.xyz ), the NM ends up registering > with the RM using only "foo". This can create problems if DNS cannot resolve > the hostname properly. > Furthermore, HDFS uses fully qualified hostnames which can end up affecting > locality matches when allocating containers based on block locations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira