hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1316) JobTracker holds stale references to retired jobs via unreported tasks
Date Tue, 22 Dec 2009 06:15:18 GMT

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

Amar Kamat updated MAPREDUCE-1316:
----------------------------------

    Description: JobTracker fails to remove _unreported_ tasks' mapping from _taskToTIPMap_
if the job finishes and retires. _Unreported tasks_ refers to tasks that were scheduled but
the tasktracker did not report back with the task status. In such cases a stale reference
is held to TaskInProgress (and thus JobInProgress) long after the job is gone leading to memory
leak.  (was: JobTracker fails to remove speculative tasks' mapping from _taskToTIPMap_ if
the job finishes and retires before the tracker (running the speculative tasks) reports back.
In such cases a stale reference is held to TaskInProgress (and thus JobInProgress) long after
the job is gone leading to memory leak.)
        Summary: JobTracker holds stale references to retired jobs via unreported tasks  
(was: JobTracker holds stale references to retired jobs via speculated tips )

> JobTracker holds stale references to retired jobs via unreported tasks 
> -----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1316
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1316
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>            Priority: Blocker
>
> JobTracker fails to remove _unreported_ tasks' mapping from _taskToTIPMap_ if the job
finishes and retires. _Unreported tasks_ refers to tasks that were scheduled but the tasktracker
did not report back with the task status. In such cases a stale reference is held to TaskInProgress
(and thus JobInProgress) long after the job is gone leading to memory leak.

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