Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <2285940.30901286483492059.JavaMail.jira@thor>
Date: Thu, 7 Oct 2010 16:31:32 -0400 (EDT)
From: "Scott Chen (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1908) DistributedRaidFileSystem does
 not handle ChecksumException correctly
In-Reply-To: <3055238.160991278016970256.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919051#action_12919051 ] 

Scott Chen commented on MAPREDUCE-1908:
---------------------------------------

Ram: Can you add one more unit test that corrupt more than one block in the stripe?

> DistributedRaidFileSystem does not handle ChecksumException correctly
> ---------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1908
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1908
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Ramkumar Vadali
>            Assignee: Ramkumar Vadali
>         Attachments: MAPREDUCE-1908.patch
>
>
> ChecksumException reports the offset of corruption within a block,
> whereas DistributedRaidFileSystem.setAlternateLocations was expecting it
> to report the offset of corruption within the file.
> The best way of dealing with a missing block/corrupt block is to just
> use the current seek offset in the file as the position of corruption.

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