hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3670) JobTracker running out of heap space
Date Tue, 01 Jul 2008 04:47:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609449#action_12609449
] 

Devaraj Das commented on HADOOP-3670:
-------------------------------------

Could you pls let us know once you get the heap dump. Also, how many nodes does the cluster
have?

> JobTracker running out of heap space
> ------------------------------------
>
>                 Key: HADOOP-3670
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3670
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Christian Kunz
>
> The JobTracker on our 0.17.0 installation runs out of heap space rather quickly, with
less than 100 jobs (at one time even after just 16 jobs).
> Running in 64-bit mode with larger heap space does not help -- it will use up all available
RAM.
> 2008-06-28 05:17:06,661 INFO org.apache.hadoop.ipc.Server: IPC Server handler 62 on 9020,
call he
> artbeat(org.apache.hadoop.mapred.TaskTrackerStatus@6f81c6, false, true, 17384) from xxx.xxx.xxx.xxx
> :51802: error: java.io.IOException: java.lang.OutOfMemoryError: GC overhead limit exceeded
> java.io.IOException: java.lang.OutOfMemoryError: GC overhead limit exceeded

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message