hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3762) Task tracker died due to OOM
Date Tue, 15 Jul 2008 23:17:32 GMT

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

Tsz Wo (Nicholas), SZE updated HADOOP-3762:

    Attachment: 3762_20080715.patch

Not sure what is going on since there is not much information in the stack trace.  

Runping, could you apply 3762_20080715.patch to get the stack trace again?  It will show more
information in the LeaseChecker stack trace.

> Task tracker died due to OOM 
> -----------------------------
>                 Key: HADOOP-3762
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3762
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Runping Qi
>            Assignee: Tsz Wo (Nicholas), SZE
>            Priority: Blocker
>             Fix For: 0.18.0
>         Attachments: 3762_20080715.patch, TaskTrackerStackTrace.txt
> When running about 100 moderate jobs on a small cluster (with 19 Task Trackers),
> the task trackers all died due to OOM.
> I got a chance to dump the jstack strace of a task tracker before it died.
> Its image size was close 4GB!
> I saw 1200+ threads of DFSClient.LeaseChecker.
> Clearly we have a severe resource leakage problem!

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

View raw message