Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <23461129.8671291676773017.JavaMail.jira@thor>
Date: Mon, 6 Dec 2010 18:06:13 -0500 (EST)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1699) JobHistory shouldn't be disabled
 for any reason
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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.