Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.22.0
-
None
-
Incompatible change, Reviewed
-
When running fsck, audit log events are not logged for listStatus and open are not logged. A new event with cmd=fsck is logged with ugi field set to the user requesting fsck and src field set to the fsck path.
Description
In Yahoo production cluster audit logs more than 50% of entries comes from FSCK. FSCK makes same Namenode method calls as clients. Because of this, the operations are logged in audit logs similar to operations invoked by the client. I want to make a change to namenode not to log operations invoked by FSCK in audit logs.
Attachments
Attachments
Issue Links
- relates to
-
HDFS-1316 Need audit log entry to indicate FSCK operation
-
- Resolved
-