[
https://issues.apache.org/jira/browse/MAPREDUCE-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gera Shegalov updated MAPREDUCE-5692:
-------------------------------------
Attachment: MAPREDUCE-5692.v02.patch
Thanks, Sandy. Here is v02 that should address your suggestions.
I reverted the change to SleepJob as it is non-essential. As for the original
reason: I use it to test features on a real job in a controlled manner. In this
case, I would start a multi-map SleepJob and suspend one attempt with SIGSTOP
to trigger speculation. Irrespective of this I can't see why SleepJob has to
hardcode disabling of speculative execution.
> Add explicit diagnostics when a task attempt is killed due to speculative
> execution
> -----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5692
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5692
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Affects Versions: 2.2.0
> Reporter: Gera Shegalov
> Assignee: Gera Shegalov
> Attachments: MAPREDUCE-5692.v01.patch, MAPREDUCE-5692.v02.patch
>
>
> We need to clearly indicate when a task attempt is killed because another
> task attempt succeeded first when speculative execution is enabled.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
