hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2446) with hadoop.security.group.mapping settings two extra INFO with every hadoop command
Date Fri, 11 Nov 2011 15:10:51 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148526#comment-13148526
] 

Kihwal Lee commented on HDFS-2446:
----------------------------------

There is no generic log level setting change that can satisfy all. With the current architecture,
the only way of achieving this is to control it through config. So, it depends on the flexibility
of deployment/installation method user is using. This can be done through passing HADOOP_*_OPS
env vars. Or something like HADOOP-7814 could help supporting multiple config in a cluster.
Since there is no code change for directly addressing this problem, I will close this.
                
> with hadoop.security.group.mapping settings two extra INFO with every hadoop command
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-2446
>                 URL: https://issues.apache.org/jira/browse/HDFS-2446
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.20.205.0
>            Reporter: Rajit Saha
>
> If we add following config parameter in core-site.xml in all the compute nodes and client
side, we get extra two INFO message in STDOUT for every hadoop command
> core-site.xml
> =============
> ...
>   <property>
>     <name>hadoop.security.group.mapping</name>
>     <value>org.apache.hadoop.security.JniBasedUnixGroupsNetgroupMapping</value>
>     <description>
>     Class for user to group mapping (get groups for a given user) for ACL
>     </description>
>   </property>
> ....
> $hadoop dfs -lsr /tmp
> 11/10/12 19:04:58 INFO util.NativeCodeLoader: Loaded the native-hadoop library
> 11/10/12 19:04:58 INFO security.JniBasedUnixGroupsMapping: Using JniBasedUnixGroupsMapping
for Group resolution
> drwx------   - hadoopqa hdfs          0 2011-10-12 19:04 /tmp/file1
> drwx------   - hadoopqa hdfs          0 2011-10-12 19:04 /tmp/file2
> $hadoop dfs -rmr -skipTrash /tmp/file2
> 11/10/12 19:04:54 INFO util.NativeCodeLoader: Loaded the native-hadoop library
> 11/10/12 19:04:54 INFO security.JniBasedUnixGroupsMapping: Using JniBasedUnixGroupsMapping
for Group resolution
> Deleted hdfs://<NN Hostname>/tmp/file2

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

        

Mime
View raw message