[
https://issues.apache.org/jira/browse/TEZ-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109588#comment-15109588
]
TezQA commented on TEZ-3052:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12783406/TEZ-3052.001.patch
against master revision e171fdd.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in :
org.apache.tez.test.TestFaultTolerance
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1429//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1429//console
This message is automatically generated.
> Task internal error due to Invalid event: T_ATTEMPT_FAILED at FAILED
> --------------------------------------------------------------------
>
> Key: TEZ-3052
> URL: https://issues.apache.org/jira/browse/TEZ-3052
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: TEZ-3052.001.patch
>
>
> A task encountered an internal error due to "Invalid event: T_ATTEMPT_FAILED
> at FAILED". The task had two outstanding attempts, as one was speculative.
> The main attempt failed causing the task to fail, and when the speculative
> attempt subsequently failed the T_ATTEMPT_FAILED triggered the invalid state
> transition.
> It appears there needs to be some hardening of the TaskImpl state machine in
> light of speculative attempt events arriving late. Besides this scenario I
> think there may be others, e.g.: speculative attempt succeeding just as
> overall task fails appears to be unhandled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
