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 "Uma Maheswara Rao G (Commented) (JIRA)" <ji...@apache.org> on 2012/03/05 03:47:01 UTC
[jira] [Commented] (HDFS-2938) Recursive delete of a large
directory makes namenode unresponsive
[ https://issues.apache.org/jira/browse/HDFS-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222134#comment-13222134 ]
Uma Maheswara Rao G commented on HDFS-2938:
-------------------------------------------
I have just verified this issue across the versions, looks 22 branch also lost the mechanism of HDFS-173.
So, we may have to back port this to 22 branch.
> Recursive delete of a large directory makes namenode unresponsive
> -----------------------------------------------------------------
>
> Key: HDFS-2938
> URL: https://issues.apache.org/jira/browse/HDFS-2938
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.22.0
> Reporter: Suresh Srinivas
> Assignee: Hari Mankude
> Attachments: HDFS-2938.patch, HDFS-2938.patch
>
>
> When deleting a large directory with millions of files, namenode holding FSNamesystem lock will make it unresponsive for other request. In this scenario HDFS-173 added a mechanism to delete blocks in smaller chunks holding the locks. With new read/write lock changes, the mechanism from HDFS-173 is lost. Need to resurrect the mechanism back. Also a good unit test/update to existing unit test is needed to catch future errors with this functionality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira