Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 20 Jul 2012 17:54:34 +0000 (UTC)
From: "Daryn Sharp (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1325258008.82928.1342806874608.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <690610644.72037.1342648416949.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HDFS-3680) Allows customized audit logging in
 HDFS FSNamesystem
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HDFS-3680?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13419=
388#comment-13419388 ]=20

Daryn Sharp commented on HDFS-3680:
-----------------------------------

Todd: good points as well about log ordering and whether the impl should en=
forcing queueing, if so, bounded/unbounded queueing.  I'm not sure there's =
a one-size-fits-all, and flexibility could become very complex.  I'm a bit =
squeamish of no queueing and leaving it up to the user since the logging is=
 inside the namesystem lock.  It'll be all too easy to add latency or even =
stall the NN entirely trying to log a write op.

While conceptually this jira is good idea, this is in a very critical porti=
on of the NN that risks dire performance impacts. I'm inclined to think/pro=
pose other audit loggers should post-process the audit file in a separate p=
rocess.


               =20
> 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
>
>
> 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 requir=
e the code to implement a log appender (and thus know what logging system i=
s actually being used underneath the fa=C3=A7ade), and parse the textual lo=
g message generated by FSNamesystem.
> I'm attaching a patch that introduces a cleaner interface for this use ca=
se.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira