[
https://issues.apache.org/jira/browse/HDFS-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas updated HDFS-173:
---------------------------------
Attachment: HDFS-173.1.patch
Attaching a patch described in my proposal above. Two changes from the proposal:
- Logging is still done with lock held to reduce changes
- Added a sleep of 1 msec between freeing up 1000 blocks. Without this, in my
test, other threads that perform namenode operations could not get the lock
frequently, during deletion. The sleep time adds up to 10 sec for 10 million
files.
> 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.
