hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krishna Ramachandran (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1699) JobHistory shouldn't be disabled for any reason
Date Wed, 30 Jun 2010 22:30:56 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Krishna Ramachandran updated MAPREDUCE-1699:

    Attachment: mapred-1699-7.patch

Revised (from Arun's review)

if logSubmitted writer fails we remove the entry from fileManager list (if not null)

Patch for an earlier release. Not for commit in trunk

> 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-3.patch, mapred-1699-5.patch,
mapred-1699-7.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.

View raw message