[
https://issues.apache.org/jira/browse/HDFS-7548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286164#comment-14286164
]
Hadoop QA commented on HDFS-7548:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12693618/HDFS-7548-v5.patch
against trunk revision 6b17eb9.
{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.qjournal.TestSecureNNWithQJM
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/9293//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9293//console
This message is automatically generated.
> Corrupt block reporting delayed until datablock scanner thread detects it
> -------------------------------------------------------------------------
>
> Key: HDFS-7548
> URL: https://issues.apache.org/jira/browse/HDFS-7548
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Rushabh S Shah
> Assignee: Rushabh S Shah
> Attachments: HDFS-7548-v2.patch, HDFS-7548-v3.patch,
> HDFS-7548-v4.patch, HDFS-7548-v5.patch, HDFS-7548.patch
>
>
> When there is one datanode holding the block and that block happened to be
> corrupt, namenode would keep on trying to replicate the block repeatedly but
> it would only report the block as corrupt only when the data block scanner
> thread of the datanode picks up this bad block.
> Requesting improvement in namenode reporting so that corrupt replica would be
> reported when there is only 1 replica and the replication of that replica
> keeps on failing with the checksum error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
