Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 18 Jun 2013 22:29:21 +0000 (UTC)
From: "Hitesh Shah (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12653554.1371582668485.136104.1371594561034@arcas>
In-Reply-To: <JIRA.12653554.1371582668485@arcas>
References: <JIRA.12653554.1371582668485@arcas>
Subject: [jira] [Updated] (YARN-848) Nodemanager does not register with RM
 using the fully qualified hostname
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hitesh Shah updated YARN-848:
-----------------------------

    Attachment: YARN-848.2.patch

Rebased against YARN-694.
                
> 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