hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3336) Direct a subset of namenode RPC events for audit logging
Date Tue, 06 May 2008 07:17:56 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594499#action_12594499

dhruba borthakur commented on HADOOP-3336:

This is a File Change Log [http://en.wikipedia.org/wiki/File_Change_Log] . It can be used
for audit purposes. It can also be used for backup and/or synchornization with remote mirror

I agree with Chris that for auditing purposes, it might be sufficient to not persist this
log. However, if we plan to use this File Change Log for backup and/or remote mirroring, then
its constraints will have to be more stringent.

> Direct a subset of namenode RPC events for audit logging 
> ---------------------------------------------------------
>                 Key: HADOOP-3336
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3336
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: dfs
>            Reporter: Chris Douglas
> A non-persistent transaction log will permit managers of HDFS installations to monitor
and reconstruct user activity in HDFS for forensic analysis and maintenance.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message