[
https://issues.apache.org/jira/browse/MAPREDUCE-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915981#action_12915981
]
Ramkumar Vadali commented on MAPREDUCE-1908:
--------------------------------------------
ant test result:
All but org.apache.hadoop.streaming.TestUlimit passed. TestUlimit failure is
unrelated to this.
ant test-patch result:
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 2 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
[exec]
[exec] +1 system tests framework. The patch passed system tests
framework compile.
[exec]
[exec]
[exec]
[exec]
[exec]
======================================================================
[exec]
======================================================================
[exec] Finished build.
[exec]
======================================================================
[exec]
======================================================================
> 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.
