tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TezQA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEZ-3102) Fetch failure of a speculated task causes job hang
Date Wed, 24 Feb 2016 22:39:18 GMT

    [ https://issues.apache.org/jira/browse/TEZ-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15165644#comment-15165644

TezQA commented on TEZ-3102:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against master revision 701e9aa.

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

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/1508//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1508//console

This message is automatically generated.

> Fetch failure of a speculated task causes job hang
> --------------------------------------------------
>                 Key: TEZ-3102
>                 URL: https://issues.apache.org/jira/browse/TEZ-3102
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Critical
>         Attachments: TEZ-3102.001.patch, TEZ-3102.002.patch, TEZ-3102.003.patch
> If a task speculates then succeeds, one task will be marked successful and the other
killed. Then if the task retroactively fails due to fetch failures the Tez AM will fail to
reschedule another task. This results in a hung job.

This message was sent by Atlassian JIRA

View raw message