You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2008/05/09 01:08:55 UTC

[jira] Updated: (HADOOP-3336) Direct a subset of namenode RPC events for audit logging

     [ https://issues.apache.org/jira/browse/HADOOP-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Douglas updated HADOOP-3336:
----------------------------------

    Attachment: 3336-0.patch

bq. if we plan to use this File Change Log for backup and/or remote mirroring, then its constraints will have to be more stringent

Agreed.

This patch exposes a general audit logging API through the commons logging interface. All audit events are at INFO level.

> 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
>         Attachments: 3336-0.patch
>
>
> 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.