[ https://issues.apache.org/jira/browse/MAPREDUCE-4646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated MAPREDUCE-4646: ----------------------------------------------- Status: Open (was: Patch Available) Good catch, Jason. Can you fix {{MRBuilderUtils.newJobReport()}} itself to also take in a diagnostics instead of doing an explicit setDiagnostics? Also, you can send a {{JobDiagnosticsUpdateEvent}} itself instead of an addDiagnostics() in the test-case. > client does not receive job diagnostics for failed jobs > ------------------------------------------------------- > > Key: MAPREDUCE-4646 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4646 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Affects Versions: 2.0.1-alpha, 0.23.0 > Reporter: Jason Lowe > Assignee: Jason Lowe > Attachments: MAPREDUCE-4646.patch > > > When a job fails the client is not showing any diagnostics. For example, > running a fail job results in this not-so-helpful message from the client: > {noformat} > 2012-09-07 21:12:00,649 INFO [main] mapreduce.Job > (Job.java:monitorAndPrintJob(1308)) - Job job_1347052207658_0001 failed with > state FAILED due to: > {noformat} > ...and nothing else to go with it indicating what went wrong. The job > diagnostics are apparently not making it back to the client. -- 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