[
https://issues.apache.org/jira/browse/MAPREDUCE-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889062#comment-13889062
]
Karthik Kambatla commented on MAPREDUCE-2217:
---------------------------------------------
IIRC, the expiration timeout is 10 minutes by default. Agree it could be a
problem if the jobs take longer than 10 minutes to localize. Is this a real
concern? If so, would bumping up the expiration timeout be an acceptable
workaround?
> 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)
