hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-2938) Recursive delete of a large directory makes namenode unresponsive
Date Wed, 15 Feb 2012 22:04:00 GMT

     [ https://issues.apache.org/jira/browse/HDFS-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Suresh Srinivas updated HDFS-2938:

          Resolution: Fixed
    Target Version/s: 0.24.0, 0.23.2  (was: 0.23.2, 0.24.0)
        Hadoop Flags: Reviewed
              Status: Resolved  (was: Patch Available)

Committed the patch to trunk and 0.23. Thank you Hari.
> 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


View raw message