[
https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-848:
-----------------------------
Description:
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 reducing
locality matches when allocating containers based on block locations.
was:
If the hostname is misconfigured to 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 reducing
locality matches when allocating containers based on block locations.
> 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
>
> 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 reducing
> 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
