hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5315) DistCp reports success even on failure.
Date Tue, 11 Jun 2013 14:41:20 GMT

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

Jason Lowe updated MAPREDUCE-5315:

    Attachment: MAPREDUCE-5315-2.patch

bq. Is there perhaps a way to throw an exception that is more useful to the user than "something
went wrong! go dig in the logs"?

Good point, attaching an updated patch that should shed a bit more light in the exception
message about a job that did not complete successfully.
> DistCp reports success even on failure.
> ---------------------------------------
>                 Key: MAPREDUCE-5315
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5315
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: distcp
>    Affects Versions: 0.23.1, 2.0.0-alpha
>            Reporter: Mithun Radhakrishnan
>            Assignee: Mithun Radhakrishnan
>            Priority: Critical
>         Attachments: MAPREDUCE-5315-2.patch, MAPREDUCE-5315.branch-0.23.patch
> DistCp doesn't check the job-status when run in blocking-mode, before returning its exit-code.
(The Yahoo-internal version did this correctly.)
> In blocking-mode, DistCp must check that the launched job runs to completion, and return
an appropriate exit-code.
> Pretty serious bug, since it affects data integrity, in Oozie-launched-DistCp actions.
> (I could've sworn I had another JIRA with this patch attached.)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message