hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sharad Agarwal (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4906) TaskTracker running out of memory after running several tasks
Date Tue, 03 Feb 2009 04:54:59 GMT

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

Sharad Agarwal updated HADOOP-4906:
-----------------------------------

    Release Note: Fix the tasktracker for OOM exception by sharing the jobconf properties
across tasks of the same job. Earlier a new instance was held for each task. With this fix,
the job level configuration properties are shared across tasks of the same job.

> TaskTracker running out of memory after running several tasks
> -------------------------------------------------------------
>
>                 Key: HADOOP-4906
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4906
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Arun C Murthy
>            Assignee: Sharad Agarwal
>            Priority: Blocker
>             Fix For: 0.19.1
>
>         Attachments: 4906_v1.patch, 4906_v2.patch, 4906_v3.patch, 4906_v4.patch, 4906_v5.patch
>
>
> Looks like the TaskTracker isn't cleaning up correctly after completed/failed tasks,
I suspect that the JobConfs aren't being deallocated. Eventually the TaskTracker runs out
of memory after running several tasks.

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