[
https://issues.apache.org/jira/browse/MAPREDUCE-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780290#comment-13780290
]
Omkar Vinit Joshi commented on MAPREDUCE-5533:
----------------------------------------------
{code}
+ handleAttempt(taskAttemptStatus);
{code}
why can't we call this everytime we are calling below method? We can skip
calling this for task attempt update instead. thoughts? thereby we don't need
to store the past ones in DefaultSpeculator.
{code}
private long speculationValue(TaskId taskID, long now)
{code}
> Speculative execution does not function for reduce
> --------------------------------------------------
>
> Key: MAPREDUCE-5533
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5533
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster
> Reporter: Tassapol Athiapinya
> Assignee: Xuan Gong
> Fix For: 2.1.1-beta
>
> Attachments: MAPREDUCE-5533.1.patch, MAPREDUCE-5533.2.patch,
> MAPREDUCE-5533.3.patch
>
>
> We have sort job where reduce attempt does not send heartbeat in timely
> manner to application master. The AM should kick off another attempt to let
> job succeeds. What we find is the job fails and there is no speculation
> happening.
--
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
