hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1699) JobHistory shouldn't be disabled for any reason
Date Wed, 14 Apr 2010 01:09:52 GMT

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

Allen Wittenauer commented on MAPREDUCE-1699:
---------------------------------------------

We just hit this as well.  Trying to build stats for capacity planning... and 'lo, we see
no job stats. :(

> 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.22.0
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message