hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-12687) SecureUtil#getByName should also try to resolve direct hostname, incase multiple loopback addresses are present in /etc/hosts
Date Mon, 16 May 2016 22:46:13 GMT

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

Vinod Kumar Vavilapalli updated HADOOP-12687:
---------------------------------------------
    Target Version/s: 2.8.0, 3.0.0-alpha1
            Priority: Blocker  (was: Major)

I am going to bump this to be a blocker for all outstanding releases.

This is causing too much pain, many JIRAs are running into this, and we are going ahead and
committing patches relatively blindly.

Either this gets fixed or INFRA-11150 moves forward.

> 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
>            Priority: Blocker
>              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)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message