[jira] [Issue Comment Deleted] (TEZ-2647) Add input causality dependency for attempts

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

     [ https://issues.apache.org/jira/browse/TEZ-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bikas Saha updated TEZ-2647:
----------------------------
    Comment: was deleted

(was: {color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12748286/TEZ-2647.1.patch
  against master revision 4f66cb4.

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

    {color:green}+1 tests included{color}.  The patch appears to include 8 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.dag.app.TestTaskAttemptListenerImplTezDag
                  org.apache.tez.dag.app.dag.impl.TestVertexImpl

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

This message is automatically generated.)

> Add input causality dependency for attempts
> -------------------------------------------
>
>                 Key: TEZ-2647
>                 URL: https://issues.apache.org/jira/browse/TEZ-2647
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: TEZ-2647.1.patch
>
>
> Attempts can have input dependencies on the producer task attempts that produced the data being consumed by the attempt.
> DataMovement events capture this dependency. In the interest of space, we need to be able to capture the dependency that matters - the one that provided the last data for the input to complete.
> For starters, we could 
> 1) have the system track the last data movement event that was sent to an attempt
> 2) then have the inputs be able to report the last relevant data movement event



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