hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-4557) Fix FSDirectory#delete when INode#cleanSubtree returns 0
Date Thu, 07 Mar 2013 22:36:14 GMT

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

Tsz Wo (Nicholas), SZE resolved HDFS-4557.

       Resolution: Fixed
    Fix Version/s: Snapshot (HDFS-2802)

I have committed this.  Thanks, Jing!
> Fix FSDirectory#delete when INode#cleanSubtree returns 0
> --------------------------------------------------------
>                 Key: HDFS-4557
>                 URL: https://issues.apache.org/jira/browse/HDFS-4557
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>            Priority: Minor
>             Fix For: Snapshot (HDFS-2802)
>         Attachments: HDFS-4557.000.patch, HDFS-4557.001.patch, HDFS-4557.002.patch, HDFS-4557.003.patch,
> Currently INode#cleanSubtree is used to delete files/directories and collect corresponding
blocks for future deletion. Its return value can be 0 even if file/dir has been deleted because
we save snapshot copies. This breaks the original logic in FSDirectory#delete since FSDirectory#delete
expects a positive value from a successful deletion.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message