[
https://issues.apache.org/jira/browse/SQOOP-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234380#comment-14234380
]
Jarek Jarcec Cecho edited comment on SQOOP-1839 at 12/4/14 5:28 PM:
--------------------------------------------------------------------
The problem is that [PreCommit parent
job|https://builds.apache.org/job/PreCommit-Admin/] that is responsible for
kicking in the [Sqoop Pre-Commit
hook|https://builds.apache.org/job/PreCommit-SQOOP-Build/] is failing at the
moment. I've looked into that a bit and it's failing on SVN errors which make
sense as Apache SVN repo is offline because of disk failures. Apache Infra is
keeping public updates via [special
blogpost|https://blogs.apache.org/infra/entry/subversion_master_undergoing_emergency_maintenance].
I've seen some successful runs after you've submitted the latest patch here
[~vybs], which is unexpected, but I assume that the Admin job is simply
misbehaving because of the SVN issues. I would wait on SVN Server to get back
up and then resubmit the patch.
was (Author: jarcec):
The problem is that [PreCommit parent
job|https://builds.apache.org/job/PreCommit-Admin/] that is responsible for
kicking in the [Sqoop Pre-Commit
hook|https://builds.apache.org/job/PreCommit-SQOOP-Build/] is failing at the
moment. I've looked into that a bit and it's failing on SVN errors which make
sense as Apache SVN repo is offline because of disk failures. I've seen some
successful runs after you've submitted the latest patch here [~vybs], which is
unexpected, but I assume that the Admin job is simply misbehaving because of
the SVN issues. I would wait on SVN Server to get back up and then resubmit the
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-v1.patch, SQOOP-1839-v2.patch,
> 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)
