[
https://issues.apache.org/jira/browse/HDFS-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107620#comment-14107620
]
Hadoop QA commented on HDFS-2975:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12663663/HDFS-2975.001.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.server.namenode.ha.TestPipelinesFailover
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/7726//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7726//console
This message is automatically generated.
> Rename with overwrite flag true can make NameNode to stuck in safemode on NN
> (crash + restart).
> -----------------------------------------------------------------------------------------------
>
> Key: HDFS-2975
> URL: https://issues.apache.org/jira/browse/HDFS-2975
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Reporter: Uma Maheswara Rao G
> Assignee: Yi Liu
> Attachments: HDFS-2975.001.patch
>
>
> When we rename the file with overwrite flag as true, it will delete the
> destination file blocks. After deleting the blocks, whenever it releases the
> fsNameSystem lock, NN can give the invalidation work to corresponding DNs to
> delete the blocks.
> Parallaly it will sync the rename related edits to editlog file. At this step
> before NN sync the edits if NN crashes, NN can stuck into safemode on
> restart. This is because block already deleted from the DN as part of
> invalidations. But dst file still exist as rename edits not persisted in log
> file and no DN will report that blocks now.
> This is similar to HDFS-2815
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
