[jira] Commented: (MAPREDUCE-661) distcp doesn't ignore read failures with -i in setup() before MapReduce job is started

["Ravi Gummadi (JIRA)" <ji...@apache.org>]

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

Ravi Gummadi commented on MAPREDUCE-661:
----------------------------------------

Failed test is not related to this patch.

I don't see an easy way to add a unit test for this. Tested manually with -i option and throwing IOException from within setup().

> distcp doesn't ignore read failures with -i in setup() before MapReduce job is started
> --------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-661
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-661
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: distcp
>    Affects Versions: 0.21.0
>            Reporter: Ravi Gummadi
>            Assignee: Ravi Gummadi
>             Fix For: 0.21.0
>
>         Attachments: d_ignore_read_failures.patch
>
>
> After HADOOP-3873, file checksums are checked in setup() before actual MapReduce job is started. And when getFileChecksum() fails with socketTimeoutException when called from setup(), distcp fails even though -i option is specified by user. Similar to how map tasks ignore read failures, setup() should also ignore them and continue processing remaining files.

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