[jira] Commented: (MAPREDUCE-1699) JobHistory shouldn't be disabled for any reason

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on MAPREDUCE-1699:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12445602/mapred-1699.patch
  against trunk revision 947758.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/207/console

This message is automatically generated.

> 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
>             Fix For: 0.20.3
>
>         Attachments: 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.