You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Rushabh S Shah (JIRA)" <ji...@apache.org> on 2014/12/18 17:03:14 UTC

[jira] [Created] (HDFS-7548) Corrupt block reporting delayed until datablock scanner thread detects it

Rushabh S Shah created HDFS-7548:
------------------------------------

             Summary: 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


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)