hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7503) Client#getRemotePrincipal NPEs when given invalid dfs.*.name
Date Thu, 22 Sep 2011 01:16:26 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112278#comment-13112278

Eli Collins commented on HADOOP-7503:

Thanks for following up Uma. I think so, a test which enables security and sets a bogus dfs.https.address
would confirm.

> 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.23.0
>            Reporter: Eli Collins
>              Labels: newbie
> 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


View raw message