[ http://issues.apache.org/jira/browse/HADOOP-293?page=all ]
Mikkel Kamstrup Erlandsen updated HADOOP-293:
---------------------------------------------
Attachment: report-error-1.patch
I've had my share of troubles regarding this too. When a task encounters an
error, all I see is:
Exception in thread "main" java.io.IOException: Job failed!
at org.apache.hadoop.mapred.JobClient.runJob(JobClient.java:357)
...
<snip useless info>
I attach a preview patch of my suggestion. It is against 0.4, but I'll forward
port it to head and integrate it more with the rest of the system, if the
approach is generally accepted by the devs. Please consider the patch as a
idea-preview, not as a serious stab at the problem.
The approach is to add a public JobStatus.lastError string, which can be set
from any throwable like JobStatus.setLastError(Throwable t). Setting this at
relevant places (fx. on errors in mapred.LocalJobRunner.run() as in the patch)
is useful for debugging purposes (for me atleast).
> map reduce job fail without reporting a reason
> ----------------------------------------------
>
> Key: HADOOP-293
> URL: http://issues.apache.org/jira/browse/HADOOP-293
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.3.1
> Reporter: Yoram Arnon
> Assigned To: Owen O'Malley
> Fix For: 0.5.0
>
> Attachments: report-error-1.patch
>
>
> Often I see in the WI reports of tasks failing without information reported
> as to the reason of the failure.
> It makes analysis and fixing the problem much harder.
> The reason for the failure should always be reported in the WI.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
