[ https://issues.apache.org/jira/browse/HDFS-15627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214387#comment-17214387 ]
Ahmed Hussein commented on HDFS-15627: -------------------------------------- [~jianghuazhu], this patch does not delete "Audit-log". The patch changes the order in which the delete event is into the audit-log, moving it up to be done before incremental deletes. The tweak is suggested by [~daryn] to make debugging easier. [~daryn] noticed that the audit-log has a lag in recording the delete-event. As a result, when you check the audit-log, you might not see anything there. However, audit-log for delete event was pending because there are so many incremental deletes. > Audit log deletes after edit is written > --------------------------------------- > > Key: HDFS-15627 > URL: https://issues.apache.org/jira/browse/HDFS-15627 > Project: Hadoop HDFS > Issue Type: Bug > Components: logging, namenode > Reporter: Ahmed Hussein > Assignee: Ahmed Hussein > Priority: Major > Attachments: HDFS-15627.001.patch > > > Deletes currently collect blocks in the write lock, write the edit, > incrementally block delete, finally +audit log+. It should be collect blocks, > edit log, +audit log+, incremental delete. Once the edit is durable it's > consistent to audit log the delete. There is no sense in deferring the audit > into the indeterminate future. > The problem occurs when thereto server hung due to large deletes but it won't > be easy to identify the problem. That should have been easily identified as > the first delete logged after the hang. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org