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/14 10:00:20 UTC
[jira] Created: (MAPREDUCE-1291) JobTracker fails to remove setup
tip mapping from taskidToTIPMap if the job gets killed before the setup
returns
JobTracker fails to remove setup tip mapping from taskidToTIPMap if the job gets killed before the setup returns
----------------------------------------------------------------------------------------------------------------
Key: MAPREDUCE-1291
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1291
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: jobtracker
Reporter: Amar Kamat
Priority: Critical
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MAPREDUCE-1291) JobTracker holds stale references
to retired jobs via setup tasks
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat resolved MAPREDUCE-1291.
-----------------------------------
Resolution: Fixed
Taken care in MAPREDUCE-1316.
> 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.
[jira] Commented: (MAPREDUCE-1291) JobTracker fails to remove setup
tip mapping from taskidToTIPMap if the job gets killed before the setup
returns
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792834#action_12792834 ]
Amar Kamat commented on MAPREDUCE-1291:
---------------------------------------
Also note that if the tasktracker running the setup returns after the job gets retired (i.e the setup task status is missing at the JobTracker), the task-id to tip mapping will not get removed. This is inline with this [comment|https://issues.apache.org/jira/browse/MAPREDUCE-1316?focusedCommentId=12792829&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12792829] on MAPREDUCE-1316.
> JobTracker fails to remove setup tip mapping from taskidToTIPMap if the job gets killed before the setup returns
> ----------------------------------------------------------------------------------------------------------------
>
> 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: Critical
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (MAPREDUCE-1291) JobTracker fails to remove setup
tip mapping from taskidToTIPMap if the job gets killed before the setup
returns
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat reassigned MAPREDUCE-1291:
-------------------------------------
Assignee: Amar Kamat
> JobTracker fails to remove setup tip mapping from taskidToTIPMap if the job gets killed before the setup returns
> ----------------------------------------------------------------------------------------------------------------
>
> 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: Critical
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1291) JobTracker holds stale references
to retired jobs via setup tasks
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (MAPREDUCE-1291) JobTracker fails to remove setup
tip mapping from taskidToTIPMap if the job gets killed before the setup
returns
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated MAPREDUCE-1291:
----------------------------------
Priority: Blocker (was: Critical)
> JobTracker fails to remove setup tip mapping from taskidToTIPMap if the job gets killed before the setup returns
> ----------------------------------------------------------------------------------------------------------------
>
> 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
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.