You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2014/03/14 23:44:44 UTC
[jira] [Resolved] (TEZ-933) Race in getting source / destination
numTasks on an Edge
[ https://issues.apache.org/jira/browse/TEZ-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Seth resolved TEZ-933.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.4.0
Thanks for the quick review. Committing. WIll create a separate jira to follow up on other potential changes required.
> Race in getting source / destination numTasks on an Edge
> --------------------------------------------------------
>
> Key: TEZ-933
> URL: https://issues.apache.org/jira/browse/TEZ-933
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 0.4.0
>
> Attachments: TEZ-933.1.txt
>
>
> Edges rely on getting properties (specifically numTasks in this case) from the source or destination vertex.
> This can end up with an incorrect value being used depending on the state of the vertex - whether the vertex has been initialized, whether the parallelism has been changed etc.
> As an example
> {code}
> edgeManager.getNumSourceTaskPhysicalOutputs(destinationVertex.getTotalTasks(), sourceTaskIndex))
> {code}
> destinationVertex.getTotalTasks() may be incorrect if the destinationVertex hasn't yet been initialized. Alternately, this value can change based on setParallelism calls.
--
This message was sent by Atlassian JIRA
(v6.2#6252)