You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2013/09/29 04:17:24 UTC

[jira] [Resolved] (HADOOP-10002) Tool's config option wouldn't work on secure clusters

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

Harsh J resolved HADOOP-10002.
------------------------------

       Resolution: Duplicate
    Fix Version/s: 2.0.3-alpha

Sorry about the noise. This should be fixed by HADOOP-9021 - turns out I wasn't looking at the right 2.0.x sources when debugging this.

> Tool's config option wouldn't work on secure clusters
> -----------------------------------------------------
>
>                 Key: HADOOP-10002
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10002
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security, util
>    Affects Versions: 2.0.0-alpha
>            Reporter: Harsh J
>            Priority: Minor
>             Fix For: 2.0.3-alpha
>
>
> The Tool framework provides a way for clients to run without classpath *-site.xml configs, by letting users pass "-conf <file>" to parse into the app's Configuration object.
> In a secure cluster config setup, such a runner will not work cause of UserGroupInformation.isSecurityEnabled() check, which is used in Server.java to determine what form of communication to use, will load statically a {{new Configuration()}} object to inspect if security is turned on during its initialization, which ignores the application config object and tries to load from classpath and ends up loading non-secure defaults.



--
This message was sent by Atlassian JIRA
(v6.1#6144)