Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 2 May 2011 21:01:03 +0000 (UTC)
From: "Tanping Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <7659335.16341.1304370063465.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-1371) One bad node can incorrectly flag many
 files as corrupt
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tanping Wang updated HDFS-1371:
-------------------------------

    Attachment: HDFS-1371.0502.patch

> One bad node can incorrectly flag many files as corrupt
> -------------------------------------------------------
>
>                 Key: HDFS-1371
>                 URL: https://issues.apache.org/jira/browse/HDFS-1371
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client, name-node
>    Affects Versions: 0.20.1
>         Environment: yahoo internal version 
> [knoguchi@gwgd4003 ~]$ hadoop version
> Hadoop 0.20.104.3.1007030707
>            Reporter: Koji Noguchi
>            Assignee: Tanping Wang
>         Attachments: HDFS-1371.04252011.patch, HDFS-1371.0502.patch
>
>
> On our cluster, 12 files were reported as corrupt by fsck even though the replicas on the datanodes were healthy.
> Turns out that all the replicas (12 files x 3 replicas per file) were reported corrupt from one node.
> Surprisingly, these files were still readable/accessible from dfsclient (-get/-cat) without any problems.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira