hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rushabh S Shah (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7548) Corrupt block reporting delayed until datablock scanner thread detects it
Date Sat, 10 Jan 2015 11:00:35 GMT

     [ https://issues.apache.org/jira/browse/HDFS-7548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rushabh S Shah updated HDFS-7548:
---------------------------------
    Status: Open  (was: Patch Available)

Thanks Daryn for the review.
Cancelling the current patch to address Daryn's comments.
Will update the patch shortly.

@Nathan: What action needs to be taken if java.io.IOException: Input/output error occurs.


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