You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2019/12/04 19:30:03 UTC

[GitHub] [hadoop-ozone] anuengineer commented on issue #288: HDDS-2506. Remove keyAllocationInfo and replication info from the auditLog

anuengineer commented on issue #288: HDDS-2506. Remove keyAllocationInfo and replication info from the auditLog
URL: https://github.com/apache/hadoop-ozone/pull/288#issuecomment-561802917
 
 
   > +1 to add replication information
   
   Why? it is a Audit log. Why do we need Replica Info? Audit is used to find out who made access and when. There is a very delicate trade-off between making the size of Audit log larger and finding critical information when we need it. Typically, an HDFS cluster would produce GBs of Audit logs per day, and processing all that information is lots of work. The replication in my mind is a debug tool, plus, you can always get that info from the OM.
   
   We have a set of Queries that we support in the Audit log tool. If we are able to write at least one query, them I am +1 for adding this to Audit Log. In fact, that should be the test for adding any field to the Audit log; we cannot consume the field what is the point of having it in the log. 
   
   Even a far-fetched hypothetical scenario is ok, but we must have some use from the auditing and security point of view to add something to the audit log.
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org