sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Veena Basavaraj (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-1839) Sqoop2: Mapreduce submission record should propogate failure info as well
Date Wed, 03 Dec 2014 21:24:12 GMT

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

Veena Basavaraj updated SQOOP-1839:
-----------------------------------
    Attachment: SQOOP-1839.patch

> Sqoop2: Mapreduce submission record should propogate failure info as well
> -------------------------------------------------------------------------
>
>                 Key: SQOOP-1839
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1839
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.4
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>             Fix For: 1.99.5
>
>         Attachments: SQOOP-1839.patch
>
>
> While investigating SQOOP-1815  and then trying to trace what the real reason for the
job failure was, we figured that the ExceptionInfo and ExceptionTrace are not sufficient,
since a job failure always does not mean it was due to an exception checked/ unchecked
> {code}
>   LOG.debug("Executed new map-reduce job with id " + jobId);
>     } catch (Exception e) {
>       request.getSummary().setException(e);
>       LOG.error("Error in submitting job", e);
>       return false;
>     }
>     return true;
>   }
> {code}
> In case of a job failure we all need  failure info in the submission record
> getFailureInfo()
> https://hadoop.apache.org/docs/current/api/org/apache/hadoop/mapred/RunningJob.html#getFailureInfo()



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message