hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1699) JobHistory shouldn't be disabled for any reason
Date Mon, 06 Dec 2010 23:06:13 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968467#action_12968467
] 

Todd Lipcon commented on MAPREDUCE-1699:
----------------------------------------

Does this still need to be put in trunk for 22?

> 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
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message