[jira] [Commented] (TEZ-2972) Ability for Tez AM to ignore node updates from YARN

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

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

TezQA commented on TEZ-2972:
----------------------------

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

    {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:red}-1 javac{color}.  The applied patch generated 20 javac compiler warnings (more than the master's current 16 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.sort.impl.TestPipelinedSorter

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

This message is automatically generated.

> Ability for Tez AM to ignore node updates from YARN
> ---------------------------------------------------
>
>                 Key: TEZ-2972
>                 URL: https://issues.apache.org/jira/browse/TEZ-2972
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: TEZ-2972.001.patch
>
>
> This is similar to MAPREDUCE-6119.  Sometimes reacting to a node update event can cause more harm than good.  For example, an UNHEALTHY node may be able to shuffle just fine.  Therefore obsoleting the output of tasks that ran on that node and re-running them simply adds more overhead to the job with no benefit.  It would be nice to be able to configure Tez to ignore node update events if desired.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)