[
https://issues.apache.org/jira/browse/HDFS-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950502#comment-13950502
]
Abhiraj Butala commented on HDFS-5683:
--------------------------------------
Hey Andrew,
I am hoping to provide a fix for this issue and I would really appreciate if
you can help me with a few beginner questions I have:
I tried following steps to observe the caching audit log messages in
hdfs-audit.log, but I don't see the logs being generated:
a) Compiled and installed the latest hadoop-trunk.
b) Updated the core-site.xml as per the documentation.
c) Updated the $HADOOP_CONF_DIR/log4j.properties to direct hdfs audit logs
to RFAAUDIT
d) Started namenode and datanode. I could see the hdfs-audit.log file being
generated in the $HADOOP_LOG_DIR/ as expected.
e) Added a directory and a file in hdfs using 'hdfs dfs' commands.
f) Created a cache pool: 'hdfs cacheadmin -addPool pool1'
g) Added a cache directive: 'hdfs cacheadmin -addDirective -path [path
added above] -pool pool1'
I was hoping steps e), f) and g) would log the audit messages in
hdfs-audit.log, but I did not see any logs there. Am I missing anything? Or
could it be that my audit logging is not setup correctly?
Thank you for your help!
> Better audit log messages for caching operations
> ------------------------------------------------
>
> Key: HDFS-5683
> URL: https://issues.apache.org/jira/browse/HDFS-5683
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Andrew Wang
> Labels: caching
>
> Right now the caching audit logs aren't that useful, e.g.
> {noformat}
> 2013-12-18 14:14:54,423 INFO FSNamesystem.audit
> (FSNamesystem.java:logAuditMessage(7362)) - allowed=true ugi=andrew
> (auth:SIMPLE) ip=/127.0.0.1 cmd=addCacheDirective src=null
> dst=null perm=null
> {noformat}
> It'd be good to include some more information when possible, like the path,
> pool, id, etc.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
