hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1699) JobHistory shouldn't be disabled for any reason
Date Tue, 27 Jul 2010 00:50:20 GMT

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

Chris Douglas updated MAPREDUCE-1699:

     Release Note:   (was: Fix committed 20.1xx)
    Fix Version/s:     (was: 0.20.3)

This was not fixed in the 0.20 branch. There are two options:

1) If the problem does not exist in trunk, please change resolution to "won't fix"
2) Reopen the bug, optionally attaching a patch for the Apache 0.20 branch

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

View raw message