tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Eagles (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TEZ-4068) Prevent new speculative attempt after task has issued canCommit to an attempt
Date Fri, 10 May 2019 10:03:00 GMT

     [ https://issues.apache.org/jira/browse/TEZ-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Eagles resolved TEZ-4068.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9.3
                   0.10.1

Thanks [~Chyler] for patch and [~yingdachen] for review. Committed patch to master and branch-0.9.

> Prevent new speculative attempt after task has issued canCommit to an attempt
> -----------------------------------------------------------------------------
>
>                 Key: TEZ-4068
>                 URL: https://issues.apache.org/jira/browse/TEZ-4068
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Jonathan Eagles
>            Assignee: Ying Han
>            Priority: Major
>             Fix For: 0.10.1, 0.9.3
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> When a running attempt calls TaskImpl#canCommit through the taskUmbilical, the TaskImpl
will issue a "go" if it is the first attempt to do so. Otherwise it will issue a "no-go".
After commitAttempt is assigned is TaskImpl, no other attempt is allowed to succeed at that
point. So a speculative attempt that is launched after commitAttempt is assigned can never
finished before the original since is will allows be given a "no-go" in the canCommit response.
In this jira, I propose to discuss disabling speculative attempts after commitAttempt has
been assigned.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message