[
https://issues.apache.org/jira/browse/HDFS-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126992#comment-13126992
]
Rajit Saha commented on HDFS-2446:
----------------------------------
Thanks to Kihwal Lee , we got a workaround as following
Adding the following in $HADOOP_CONF_DIR/log4j.properties in only client side,
get rid of two extra INFO logging
log4j.logger.org.apache.hadoop.security.JniBasedUnixGroupsMapping=WARN,console
log4j.logger.org.apache.hadoop.util.NativeCodeLoader=WARN,console
> 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
