hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3680) Allows customized audit logging in HDFS FSNamesystem
Date Wed, 01 Aug 2012 23:17:03 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426984#comment-13426984
] 

Suresh Srinivas commented on HDFS-3680:
---------------------------------------

bq. I can't really see a scenario where you'd have more than one custom logger
Well now that it is list, we cannot predict on how it gets used.

bq. Not sure what you mean by "in sync"
Given that on the first exception we throw away a logger, a logger could miss whole bunch
of audit logs. One could envision an audit log that cannot miss entries. So a mechanism to
bring the out of sync audit logger "in sync" will be needed. 

bq. See my comment on 20/Jul/12 . I think that's overkill and creates more problems than it
solves.
I read through the comments dated 20/Jul. I am not sure I understand why it creates more problems.
As regards to overkill, we are introducing pluggability in a critical part. It could result
in service availability issue. So lets give due consideration even if it is overkill.

bq. Does the system need a mechanism to add/remove audit loggers? When a failed logger is
fixed, do we need a way to refresh the audit logger so it is picked up by the Namenode again?
Please address this previous comment as well.
                
> Allows customized audit logging in HDFS FSNamesystem
> ----------------------------------------------------
>
>                 Key: HDFS-3680
>                 URL: https://issues.apache.org/jira/browse/HDFS-3680
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 2.0.0-alpha
>            Reporter: Marcelo Vanzin
>            Assignee: Marcelo Vanzin
>            Priority: Minor
>         Attachments: accesslogger-v1.patch, accesslogger-v2.patch, hdfs-3680-v3.patch,
hdfs-3680-v4.patch, hdfs-3680-v5.patch
>
>
> Currently, FSNamesystem writes audit logs to a logger; that makes it easy to get audit
logs in some log file. But it makes it kinda tricky to store audit logs in any other way (let's
say a database), because it would require the code to implement a log appender (and thus know
what logging system is actually being used underneath the fa├žade), and parse the textual
log message generated by FSNamesystem.
> I'm attaching a patch that introduces a cleaner interface for this use case.

--
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

       

Mime
View raw message