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 "Bob Liu (JIRA)" <ji...@apache.org> on 2014/02/02 19:46:09 UTC
[jira] [Commented] (MAPREDUCE-2217) The expire launching task
should cover the UNASSIGNED task
[ https://issues.apache.org/jira/browse/MAPREDUCE-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889019#comment-13889019 ]
Bob Liu commented on MAPREDUCE-2217:
------------------------------------
Have you folks take Distributed Cache into consideration? During a large cache download, tasktrackers are being put in the "UNASSIGNED" stated as well, does that means jobs with "large" distributed cache won't even get a chance to launch at all?
> The expire launching task should cover the UNASSIGNED task
> ----------------------------------------------------------
>
> Key: MAPREDUCE-2217
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2217
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.23.0, 1.1.1
> Reporter: Scott Chen
> Assignee: Karthik Kambatla
> Fix For: 1.2.0
>
> Attachments: MAPREDUCE-2217.1.txt, MR-2217.patch, MR-2217.patch, expose-bug-mr-2217.patch
>
>
> The ExpireLaunchingTask thread kills the task that are scheduled but not responded.
> Currently if a task is scheduled on tasktracker and for some reason tasktracker cannot put it to RUNNING.
> The task will just hang in the UNASSIGNED status and JobTracker will keep waiting for it.
> JobTracker.ExpireLaunchingTask should be able to kill this task.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)