hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-7503) Client#getRemotePrincipal NPEs when given invalid dfs.*.name
Date Wed, 03 Aug 2011 02:24:27 GMT
Client#getRemotePrincipal NPEs when given invalid dfs.*.name
------------------------------------------------------------

                 Key: HADOOP-7503
                 URL: https://issues.apache.org/jira/browse/HADOOP-7503
             Project: Hadoop Common
          Issue Type: Bug
          Components: ipc, security
    Affects Versions: 0.20.203.0, 0.23.0
            Reporter: Eli Collins


The following code in Client#getRemotePrincipal NPEs if security is enabled and dfs.https.address,
dfs.secondary.http.address, dfs.secondary.https.address, or fs.default.name, has an invalid
value (eg hdfs://foo.bar.com.foo.bar.com:1000). We should check address.checkAddress() for
null (or check this earlier)  and give a more helpful error message.

{noformat}
  return SecurityUtil.getServerPrincipal(conf.get(serverKey), address
    .getAddress().getCanonicalHostName());
{noformat}


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message