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 "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2013/05/07 00:50:19 UTC

[jira] [Resolved] (HDFS-4800) Fix INodeDirectoryWithSnapshot#cleanDeletedINode

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

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

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

I have committed this.  Thanks, Jing!
                
> Fix INodeDirectoryWithSnapshot#cleanDeletedINode
> ------------------------------------------------
>
>                 Key: HDFS-4800
>                 URL: https://issues.apache.org/jira/browse/HDFS-4800
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>            Priority: Minor
>             Fix For: Snapshot (HDFS-2802)
>
>         Attachments: HDFS-4800.001.patch
>
>
> HDFS-4791 updated and fixed the deletion logic for reference node, but did not update INodeDirectoryWithSnapshot#cleanDeletedINode. When deleting a snapshot s, after we merge s1 to its prior snapshot s0, cleanDeletedINode is called to destroy the files/directories that were created after taking snapshot s0. However, if a node is in the deleted list of s1 because of renaming, we should not destroy the node and its subtree, but just continue the normal snapshot deletion process.

--
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