Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1819624582.1238716752930.JavaMail.jira@brutus>
Date: Thu, 2 Apr 2009 16:59:12 -0700 (PDT)
From: "Hairong Kuang (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-5605) All the replicas incorrectly got
 marked as corrupt.
In-Reply-To: <1716366793.1238545310640.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hairong Kuang updated HADOOP-5605:
----------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this.

> All the replicas incorrectly got marked as corrupt.
> ---------------------------------------------------
>
>                 Key: HADOOP-5605
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5605
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.20.0
>            Reporter: Raghu Angadi
>            Assignee: Hairong Kuang
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: reportBadBlock.patch, reportBadBlock1.patch, reportBadBlock2.patch
>
>
> NameNode does not handle {{reportBadBlocks()}} properly. As a result, when DataNode reports the corruption (only in the case of block transfer between two datanodes), further attempts to replicate the block end up marking all the replicas as corrupt!
> From the implementation, it looks like NN incorrectly uses the block object used in RPC to queue to neededReplication queue instead of using internal block object. 
> will include an actual example in the next comment.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.