You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Kuhu Shukla (JIRA)" <ji...@apache.org> on 2016/08/05 18:11:21 UTC

[jira] [Updated] (TEZ-3317) Speculative execution starts too early due to 0 progress

     [ 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.002.patch

Updated preliminary patch for OrderedKVInput case and made progress reporting timer based. The weight on all input progress values right now is 1. {{SleepProcessor}} and {{MergedLogicalInput}} will be addressed next. I plan to make some changes to PigProcessor and test out multiple inputs case. The delay and period for the timer are hard coded for now since the processor is missing a conf object to work out of.

> 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
>
>
> 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)