[ https://issues.apache.org/jira/browse/HDFS-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057225#comment-14057225 ]
Hadoop QA commented on HDFS-6647: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12654884/HDFS-6647.v2.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.web.TestWebHDFSXAttr org.apache.hadoop.hdfs.server.namenode.TestDeleteRace {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/7318//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7318//console This message is automatically generated. > 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 > Attachments: HDFS-6647-failing-test.patch, HDFS-6647.patch, > HDFS-6647.v2.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)