[
https://issues.apache.org/jira/browse/TEZ-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kuhu Shukla updated TEZ-3317:
-----------------------------
Attachment: TEZ-3317.005.patch
Added a test, a synchronized block to {{getProgress}} to access {{rawIter}} in
{{OrderedKVInput}} and kept {{TimerTask}} for progress since we may not care
about Exceptions thrown during reporting progress since we want tasks to not
fail if the progress reporting task fails. Appreciate any comments on those
decisions. Thanks!
> Speculative execution starts too early due to 0 progress
> --------------------------------------------------------
>
> Key: TEZ-3317
> URL: https://issues.apache.org/jira/browse/TEZ-3317
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Jonathan Eagles
> Assignee: Kuhu Shukla
> Attachments: TEZ-3317.001.patch, TEZ-3317.002.patch,
> TEZ-3317.003.patch, TEZ-3317.004.patch, TEZ-3317.005.patch
>
>
> Don't know at this point if this is a tez or a PigProcessor issue. There is
> some setProgress chain that is keeping task progress from being correctly
> reported. Task status is always zero, so as soon as the first task finishes,
> tasks up to the speculation limit are always launched.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
