[
https://issues.apache.org/jira/browse/HDFS-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071630#comment-14071630
]
Hadoop QA commented on HDFS-5723:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12657310/HDFS-5723.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 2 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.TestNamenodeCapacityReport
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/7440//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7440//console
This message is automatically generated.
> Append failed FINALIZED replica should not be accepted as valid when that
> block is underconstruction
> ----------------------------------------------------------------------------------------------------
>
> Key: HDFS-5723
> URL: https://issues.apache.org/jira/browse/HDFS-5723
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.2.0
> Reporter: Vinayakumar B
> Assignee: Vinayakumar B
> Attachments: HDFS-5723.patch, HDFS-5723.patch, HDFS-5723.patch
>
>
> Scenario:
> 1. 3 node cluster with
> dfs.client.block.write.replace-datanode-on-failure.enable set to false.
> 2. One file is written with 3 replicas, blk_id_gs1
> 3. One of the datanode DN1 is down.
> 4. File was opened with append and some more data is added to the file and
> synced. (to only 2 live nodes DN2 and DN3)-- blk_id_gs2
> 5. Now DN1 restarted
> 6. In this block report, DN1 reported FINALIZED block blk_id_gs1, this should
> be marked corrupted.
> but since NN having appended block state as UnderConstruction, at this time
> its not detecting this block as corrupt and adding to valid block locations.
> As long as the namenode is alive, this datanode also will be considered as
> valid replica and read/append will fail in that datanode.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
