Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 16 Jan 2015 22:32:35 +0000 (UTC)
From: "Rushabh S Shah (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12762614.1418918560000.105916.1421447555813@Atlassian.JIRA>
In-Reply-To: <JIRA.12762614.1418918560000@Atlassian.JIRA>
References: <JIRA.12762614.1418918560000@Atlassian.JIRA>
 <JIRA.12762614.1418918560395@arcas>
Subject: [jira] [Updated] (HDFS-7548) Corrupt block reporting delayed until
 datablock scanner thread detects it
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

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