[
https://issues.apache.org/jira/browse/MAPREDUCE-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876058#action_12876058
]
Hadoop QA commented on MAPREDUCE-1699:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12446441/mapred-1699-2.patch
against trunk revision 951832.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/225/console
This message is automatically generated.
> JobHistory shouldn't be disabled for any reason
> -----------------------------------------------
>
> Key: MAPREDUCE-1699
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1699
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.20.2
> Reporter: Arun C Murthy
> Assignee: Krishna Ramachandran
> Fix For: 0.20.3
>
> Attachments: mapred-1699-1.patch, mapred-1699-2.patch,
> mapred-1699.patch
>
>
> Recently we have had issues with JobTracker silently disabling job-history
> and starting to keep all completed jobs in memory. This leads to OOM on the
> JobTracker. We should never do this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
