You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Amar Kamat (JIRA)" <ji...@apache.org> on 2009/12/19 20:05:18 UTC
[jira] Updated: (MAPREDUCE-1291) JobTracker holds stale references
to retired jobs via setup tasks
[ https://issues.apache.org/jira/browse/MAPREDUCE-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated MAPREDUCE-1291:
----------------------------------
Description:
JobTracker fails to remove setup tip mapping from taskidToTIPMap if the job gets killed before the setup returns.
Here is the scenario :
1) job inits
2) setup task is launched on tt1 and an entry is made in taskidToTIPMap
3) job is killed
4) cleanup gets launched on tt2
5) cleanup returns KILLING the job and removing all the *completed* setup/map/reduce task mappings from taskidToTIPMap. Here the setup is still RUNNING state.
6) job completes and all the map/reduce mappings from taskidToTIPMap are removed
In the end the setup tip still lingers in the taskidToTIPMap map. Because of the backreference from the tip to jip, the whole job stays in memory forever.
was:
Here is the scenario :
1) job inits
2) setup task is launched on tt1 and an entry is made in taskidToTIPMap
3) job is killed
4) cleanup gets launched on tt2
5) cleanup returns KILLING the job and removing all the *completed* setup/map/reduce task mappings from taskidToTIPMap. Here the setup is still RUNNING state.
6) job retires and all the map/reduce mappings from taskidToTIPMap are removed
In the end the setup tip still lingers in the taskidToTIPMap map. Because of the backreference from the tip to jip, the whole job stays in memory forever.
Summary: JobTracker holds stale references to retired jobs via setup tasks (was: JobTracker fails to remove setup tip mapping from taskidToTIPMap if the job gets killed before the setup returns)
> JobTracker holds stale references to retired jobs via setup tasks
> -----------------------------------------------------------------
>
> Key: MAPREDUCE-1291
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1291
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Priority: Blocker
>
> JobTracker fails to remove setup tip mapping from taskidToTIPMap if the job gets killed before the setup returns.
> Here is the scenario :
> 1) job inits
> 2) setup task is launched on tt1 and an entry is made in taskidToTIPMap
> 3) job is killed
> 4) cleanup gets launched on tt2
> 5) cleanup returns KILLING the job and removing all the *completed* setup/map/reduce task mappings from taskidToTIPMap. Here the setup is still RUNNING state.
> 6) job completes and all the map/reduce mappings from taskidToTIPMap are removed
>
> In the end the setup tip still lingers in the taskidToTIPMap map. Because of the backreference from the tip to jip, the whole job stays in memory forever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.