zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mohammad Arshad (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-1260) Audit logging in ZooKeeper servers.
Date Wed, 12 Sep 2018 15:11:00 GMT

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

Mohammad Arshad commented on ZOOKEEPER-1260:

To assess the performance impact of audit log feature I created, deleted and set data 5000
times on three types of clusters. Here is performance readings grouped by cluster type
 * ZooKeeper package does not have audit log feature.
   create=14776 ms
   setData=12223 ms
   delete=12599 ms
 * ZooKeeper package have audit log feature but it is disabled by configuration
   create=15161 ms
   setData=13328 ms
   delete=13046 ms
 * ZooKeeper package have audit log feature and it is enabled
   create=17364 ms
   setData=13612 ms
   delete=14174 ms

> 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
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.6.0, 3.5.5
>         Attachments: ZOOKEEPER-1260-01.patch, zookeeperAuditLogs.pdf
>          Time Spent: 10m
>  Remaining Estimate: 0h
> 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