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

Hudson commented on HDFS-6647:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1828 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1828/])
HDFS-6647. Edit log corruption when pipeline recovery occurs for deleted file 
present in snapshot. Contributed by Kihwal Lee. (kihwal: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1609543)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/snapshot/TestUpdatePipelineWithSnapshots.java


> Edit log corruption when pipeline recovery occurs for deleted file present in 
> snapshot
> --------------------------------------------------------------------------------------
>
>                 Key: HDFS-6647
>                 URL: https://issues.apache.org/jira/browse/HDFS-6647
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode, snapshots
>    Affects Versions: 2.4.1
>            Reporter: Aaron T. Myers
>            Assignee: Kihwal Lee
>            Priority: Blocker
>             Fix For: 3.0.0, 2.5.0
>
>         Attachments: HDFS-6647-failing-test.patch, HDFS-6647.patch, 
> HDFS-6647.v2.patch, HDFS-6647.v3.patch
>
>
> I've encountered a situation wherein an OP_UPDATE_BLOCKS can appear in the 
> edit log for a file after an OP_DELETE has previously been logged for that 
> file. Such an edit log sequence cannot then be successfully read by the 
> NameNode.
> More details in the first comment.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to