[
https://issues.apache.org/jira/browse/HDFS-12036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16206071#comment-16206071
]
Kuhu Shukla commented on HDFS-12036:
------------------------------------
[~HuafengWang], [~drankye], was the intent of this patch to log all
IOExceptions as well, since that is not what most FSNameSystem calls do at the
moment. My understanding is have audit logs for AccessControlException
(allowed=false) and in successful cases (allowed=true) since logging
allowed=false in the case of IOException could be misleading. Let me know your
thoughts on this and I will rebase my patch for HDFS-11246 accordingly. Thanks!
> Add audit log for some erasure coding operations
> ------------------------------------------------
>
> Key: HDFS-12036
> URL: https://issues.apache.org/jira/browse/HDFS-12036
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.0.0-alpha4
> Reporter: Wei-Chiu Chuang
> Assignee: Huafeng Wang
> Labels: hdfs-ec-3.0-must-do
> Fix For: 3.0.0-beta1
>
> Attachments: HDFS-12036.001.patch, HDFS-12036.002.patch,
> HDFS-12036.003.patch
>
>
> These three FSNameSystem operations do not yet record audit logs. I am not
> sure how useful these audit logs would be, but thought I should file them so
> that they don't get dropped if they turn out to be needed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
