hadoop-hdfs-issues mailing list archives

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

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

Kihwal Lee commented on HDFS-7548:
----------------------------------

+1 the patch looks good.
The test case is failing even without this patch and the patch was not changing anything related
to it.

> 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)

Mime
View raw message