[ 
https://issues.apache.org/jira/browse/HDFS-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650798#comment-13650798
 ] 

Hudson commented on HDFS-4800:
------------------------------

Integrated in Hadoop-Hdfs-Snapshots-Branch-build #176 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-Snapshots-Branch-build/176/])
    HDFS-4800. Fix INodeDirectoryWithSnapshot#cleanDeletedINode.  Contributed 
by Jing Zhao (Revision 1479707)

     Result = FAILURE
szetszwo : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1479707
Files : 
* 
/hadoop/common/branches/HDFS-2802/hadoop-hdfs-project/hadoop-hdfs/CHANGES.HDFS-2802.txt
* 
/hadoop/common/branches/HDFS-2802/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/INodeReference.java
* 
/hadoop/common/branches/HDFS-2802/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/snapshot/INodeDirectoryWithSnapshot.java

                
> 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

Reply via email to