[
https://issues.apache.org/jira/browse/HDFS-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749391#action_12749391
]
Raghu Angadi commented on HDFS-173:
-----------------------------------
couple of comments :
# deleting a file and and deleting a directory takes different code paths.
Earlier it was the same. I think it is better keep one code path. It will
simplify the patch. We need only one of {{FSDirectory.unlinkDirectory()}} or
{{FSDirectory.delete()}}.
# The sleep is invoked before rather than after the block deletion. results in
one redundant sleep and limits deletion rate.
#* How badly were the other threads starved without the sleep? Hopefully we
don't need the sleep.
> Recursively deleting a directory with millions of files makes NameNode
> unresponsive for other commands until the deletion completes
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-173
> URL: https://issues.apache.org/jira/browse/HDFS-173
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Attachments: HDFS-173.1.patch, HDFS-173.patch
>
>
> Delete a directory with millions of files. This could take several minutes
> (observed 12 mins for 9 million files). While the operation is in progress
> FSNamesystem lock is held and the requests from clients are not handled until
> deletion completes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
