[
https://issues.apache.org/jira/browse/MAPREDUCE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756930#action_12756930
]
Chris Douglas commented on MAPREDUCE-995:
-----------------------------------------
{noformat}
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 2 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] -1 release audit. The applied patch generated 175 release
audit warnings (more than the trunk's current 0 warnings).
{noformat}
The release audit warning is clearly spurious.
> JobHistory should handle cases where task completion events are generated
> after job completion event
> ----------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-995
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-995
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Jothi Padmanabhan
> Assignee: Jothi Padmanabhan
> Priority: Critical
> Attachments: M995-2.patch, mapred-995-v1.patch, mapred-995.patch
>
>
> It is apparently possible, in certain circumstances (failed job, for
> example), for the job history to get task completion events after the job
> completion event. This currently causes NPE in job history.
> Thanks Hong for identifying this issue
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
