hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5110) Long task launch delays can lead to multiple parallel attempts of the task
Date Mon, 15 Apr 2013 23:46:15 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632377#comment-13632377
] 

Arun C Murthy commented on MAPREDUCE-5110:
------------------------------------------

[~kkambatl] Sorry if I wasn't clear. 

My point is simple: The JT already has code to deal with slow launches i.e. ExpireLaunchingTasks.
What benefit do we get by re-implementing this on TT? Why not reduce the timeout on JT? 
                
> 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

Mime
View raw message