You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Ahmed Hussein (Jira)" <ji...@apache.org> on 2020/10/12 18:34:00 UTC
[jira] [Work started] (HDFS-15627) Audit log deletes after edit is
written
[ https://issues.apache.org/jira/browse/HDFS-15627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on HDFS-15627 started by Ahmed Hussein.
--------------------------------------------
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org