You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2016/01/08 10:09:40 UTC
[jira] [Reopened] (HADOOP-12687) SecureUtil#getByName should also
try to resolve direct hostname, incase multiple loopback addresses are
present in /etc/hosts
[ https://issues.apache.org/jira/browse/HADOOP-12687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohith Sharma K S reopened HADOOP-12687:
----------------------------------------
Reverted the issue commit, and reopening the issue.
> SecureUtil#getByName should also try to resolve direct hostname, incase multiple loopback addresses are present in /etc/hosts
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-12687
> URL: https://issues.apache.org/jira/browse/HADOOP-12687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Junping Du
> Assignee: Sunil G
> Labels: security
> Attachments: 0001-YARN-4352.patch, 0002-YARN-4352.patch, 0003-HADOOP-12687.patch, 0004-HADOOP-12687.patch
>
>
> From https://builds.apache.org/job/PreCommit-YARN-Build/9661/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client-jdk1.7.0_79.txt, we can see the tests in TestYarnClient, TestAMRMClient and TestNMClient get timeout which can be reproduced locally.
> When {{/etc/hosts}} has multiple loopback entries, {{InetAddress.getByName(null)}} will be returning the first entry present in etc/hosts. Hence its possible that machine hostname can be second in list and cause {{UnKnownHostException}}.
> Suggesting a direct resolve for such hostname scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)