hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7548) Corrupt block reporting delayed until datablock scanner thread detects it
Date Thu, 22 Jan 2015 14:21:42 GMT

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

Hudson commented on HDFS-7548:

FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #78 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/78/])
HDFS-7548. Corrupt block reporting delayed until datablock scanner thread detects it. Contributed
by Rushabh Shah. (kihwal: rev c0af72c7f74b6925786e24543cac433b906dd6d3)
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/fsdataset/impl/FsDatasetImpl.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BlockPoolSliceScanner.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BlockSender.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataBlockScanner.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDatanodeBlockScanner.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java

> 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
>             Fix For: 2.7.0
>         Attachments: HDFS-7548-v2.patch, HDFS-7548-v3.patch, HDFS-7548-v4.patch, HDFS-7548-v5.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

View raw message