[
https://issues.apache.org/jira/browse/HDFS-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743285#action_12743285
]
Koji Noguchi commented on HDFS-173:
-----------------------------------
bq. A related problem is that a Namenode server handler thread will remain busy
during all this time. Is that a problem that need to be solved too?
In our clusters, this isn't a problem since it's either Namenode's expunge
thread or ops deleting the Trash.
Another approach could be to split the large directory on the client side and
delete chunk at a time.
(I'm assuming there's no contract for delete to be atomic.)
> 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
>
> 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.
