[ 
https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687353#comment-13687353
 ] 

Hadoop QA commented on YARN-848:
--------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12588472/YARN-848.3.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 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/1337//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1337//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.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

Reply via email to