You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Eli Collins (JIRA)" <ji...@apache.org> on 2011/02/01 05:28:29 UTC
[jira] Updated: (MAPREDUCE-1699) JobHistory shouldn't be disabled
for any reason
[ https://issues.apache.org/jira/browse/MAPREDUCE-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated MAPREDUCE-1699:
-----------------------------------
Fix Version/s: 0.23.0
0.22.0
> 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.22.0, 0.23.0
>
> Attachments: mapred-1699-1.patch, mapred-1699-2.patch, mapred-1699-3.patch, mapred-1699-5.patch, mapred-1699-7.patch, mapred-1699-8.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira