hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4448) Allow HA NN to start in secure mode with wildcard address configured
Date Thu, 23 Apr 2015 12:01:42 GMT

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

Hudson commented on HDFS-4448:
------------------------------

SUCCESS: Integrated in Hadoop-Yarn-trunk #906 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/906/])
HDFS-4448. Allow HA NN to start in secure mode with wildcard address configured (atm via asuresh)
(Arun Suresh: rev baf8bc6c488de170d2caf76d9fa4c99faaa8f1a6)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSUtil.java


> Allow HA NN to start in secure mode with wildcard address configured
> --------------------------------------------------------------------
>
>                 Key: HDFS-4448
>                 URL: https://issues.apache.org/jira/browse/HDFS-4448
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha, namenode, security
>    Affects Versions: 2.0.3-alpha
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>             Fix For: 2.8.0
>
>         Attachments: HDFS-4448.2.patch, HDFS-4448.patch, HDFS-4448.patch
>
>
> Currently if one tries to configure HA NNs use the wildcard HTTP address when security
is enabled, the NN will fail to start with an error like the following:
> {code}
> java.lang.IllegalArgumentException: java.io.IOException: Cannot use a wildcard address
with security. Must explicitly set bind address for Kerberos
> {code}
> This is the case even if one configures an actual address for the other NN's HTTP address.
There's no good reason for this, since we now check for the local address being set to 0.0.0.0
and determine the canonical hostname for Kerberos purposes using {{InetAddress.getLocalHost().getCanonicalHostName()}},
so we should remove the restriction.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message