zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-1260) Audit logging in ZooKeeper servers.
Date Mon, 11 Sep 2017 20:34:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161941#comment-16161941

ASF GitHub Bot commented on ZOOKEEPER-1260:

Github user hanm commented on the issue:

    @arshadmohammad Audit logging, when enabled, will for sure degrade performance as it adds
additional IO cost. Have you done any sort of performance evaluation so we can roughly get
an idea of what kind of performance expectation we should have when audit logging is enabled?

    Depends on how the performance degraded on different use cases, you might want to consider
adding an async version of audit logging otherwise this feature might not be usable (note
I am just guessing on the perf numbers here). Similar case happened on HDFS where an async
audit logging was added to avoid degrading performance on hotspots.

> Audit logging in ZooKeeper servers.
> -----------------------------------
>                 Key: ZOOKEEPER-1260
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1260
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: server
>            Reporter: Mahadev konar
>            Assignee: Mohammad Arshad
>             Fix For: 3.5.4, 3.6.0
>         Attachments: ZOOKEEPER-1260-01.patch, zookeeperAuditLogs.pdf
> Lots of users have had questions on debugging which client changed what znode and what
updates went through a znode. We should add audit logging as in Hadoop (look at Namenode Audit
logging) to log which client changed what in the zookeeper servers. This could just be a log4j
audit logger.

This message was sent by Atlassian JIRA

View raw message