[
https://issues.apache.org/jira/browse/TEZ-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652722#comment-14652722
]
Rajesh Balamohan commented on TEZ-2647:
---------------------------------------
lgtm. +1.
Very minor comment. In VertexImpl, should getTask() is already invoked for
getting events in the begining. Should it be reused to avoid getTask() again
(just to avoid readlock?).
>>
getTask(attemptID.getTaskID()).getAttempt(attemptID).setLastEventSent(events.get(events.size()
- 1));
>>
> 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)
