[jira] [Commented] (TEZ-3910) Single node can cause Tez job to fail during shuffle

["TezQA (JIRA)" <ji...@apache.org>]

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

TezQA commented on TEZ-3910:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12931064/TEZ-3910.004.patch
  against master revision 12ff937.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 9 new or modified test files.

      {color:red}-1 javac{color}.  The applied patch generated 178 javac compiler warnings (more than the master's current 177 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.runtime.library.common.TestValuesIterator

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/2856//testReport/
Javac warnings: https://builds.apache.org/job/PreCommit-TEZ-Build/2856//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2856//console

This message is automatically generated.


> Single node can cause Tez job to fail during shuffle
> ----------------------------------------------------
>
>                 Key: TEZ-3910
>                 URL: https://issues.apache.org/jira/browse/TEZ-3910
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.9.1
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>            Priority: Major
>         Attachments: TEZ-3910.001.patch, TEZ-3910.002.patch, TEZ-3910.003.patch, TEZ-3910.004.patch
>
>
> There is a race where a downstream task that is running into fetch failures due to bad output from the upstream task can continue to blame itself for the failure before the AM can do a re-run of the upstream offending task and fix the fetch failure. This causes the DAG to fail even if a single node fails.



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