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] [Created] (TEZ-4068) Prevent new speculative attempt after task has issued canCommit to an attempt
Date Wed, 08 May 2019 20:42:00 GMT
Jonathan Eagles created TEZ-4068:
------------------------------------

             Summary: 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


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