[
https://issues.apache.org/jira/browse/TEZ-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648441#comment-14648441
]
Rajesh Balamohan commented on TEZ-2633:
---------------------------------------
Checked mainly on the vertexManagers
- ShuffleVertexManager - Would there be a corner case when schedulePendingTasks
is in the middle of updating scheduledTasks with the current value of
lastSourceAttemptCompleted & additional completion events arrive (e.g
onVertexStarted had some events upfront and onSourceTaskCompleted getting
invoked later), but unable to update the lastSourceAttemptCompleted due to
synchronization barrier?
- Same applies for InputReadyVertexManager
> Allow VertexManagerPlugins to receive and report based on attempts instead of
> tasks
> -----------------------------------------------------------------------------------
>
> Key: TEZ-2633
> URL: https://issues.apache.org/jira/browse/TEZ-2633
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-2633.1.patch
>
>
> If the same event is sent from an attempt and its retry then there is no way
> to differentiate between them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
