[
https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687311#comment-13687311
]
Hadoop QA commented on YARN-848:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12588471/YARN-848.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 22 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1336//console
This message is automatically generated.
> 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
> Attachments: YARN-848.1.patch, YARN-848.2.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
