hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-4448) HA NN does not start with wildcard address configured for other NN when security is enabled
Date Tue, 29 Jan 2013 04:09:12 GMT
Aaron T. Myers created HDFS-4448:
------------------------------------

             Summary: HA NN does not start with wildcard address configured for other NN when
security is enabled
                 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


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 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

Mime
View raw message