hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3395) NN doesn't start with HA+security enabled and HTTP address set to
Date Thu, 10 May 2012 05:18:01 GMT

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

Aaron T. Myers updated HDFS-3395:

    Attachment: HDFS-3395.patch

Here's a patch which addresses the issue.

No tests are included since security has to be enabled to test this code path. I tested it
manually by setting the NN HTTP addresses to be wildcard in a secure HA setup, and confirming
that checkpoints still proceed as expected.

This patch also takes the liberty of fixing two typos I noticed in javadocs in the course
of researching this bug.
> NN doesn't start with HA+security enabled and HTTP address set to
> -------------------------------------------------------------------------
>                 Key: HDFS-3395
>                 URL: https://issues.apache.org/jira/browse/HDFS-3395
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 2.0.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>         Attachments: HDFS-3395.patch
> DFSUtil#substituteForWildcardAddress subs in a default hostname if the given hostname
is However, this function throws an exception if the given hostname is set to
and security is enabled, regardless of whether the default hostname is also This
function shouldn't throw an exception unless both addresses are set to

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message