[
https://issues.apache.org/jira/browse/MAPREDUCE-5110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618468#comment-13618468
]
Arun C Murthy commented on MAPREDUCE-5110:
------------------------------------------
bq. All this said, if you are uncomfortable with the JT changes, I can restrict
the changes to TT.
[~kkambatl] As I said in my comment, I'm more worried about TT-side than JT...
The JT already has code to catch slow launches i.e. ExpireLaunchingTasks
thread. Why do we need to re-invent it on TT side? IAC, the problem we are
trying to solve here is fairly obscure i.e. a hardware issue causing slow task
launches... even that is already tracked by JT, right?
> Long task launch delays can lead to multiple parallel attempts of the task
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-5110
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5110
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 1.1.2
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: expose-mr-5110.patch, mr-5110.patch, mr-5110.patch,
> mr-5110-tt-only.patch
>
>
> If a task takes too long to launch, the JT expires the task and schedules
> another attempt. The earlier attempt can start after the later attempt
> leading to two parallel attempts running at the same time. This is
> particularly an issue if the user turns off speculation and expects a single
> attempt of a task to run at any point in time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
