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 2017/02/24 20:54:44 UTC
[jira] [Comment Edited] (TEZ-3625) Dag.getVertex should obtain a
readlock
[ https://issues.apache.org/jira/browse/TEZ-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883486#comment-15883486 ]
Siddharth Seth edited comment on TEZ-3625 at 2/24/17 8:54 PM:
--------------------------------------------------------------
This change ended up resulting in a race and occasional deadlock between dagCompletion and some call from the VertexManagerPlugin for dags with 0 fragments. Reverting.
The extra appThreads has caused quite a few problems. Will look to see how this particular deadlock can be avoided. Ideally, there should be a readLock on getVertex.
was (Author: sseth):
This change ended up resulting in a race and occasional deadlock between dagCompletion and some call from the VertexManagerPlugin for dags with 0 fragments. Reverting.
> Dag.getVertex should obtain a readlock
> --------------------------------------
>
> Key: TEZ-3625
> URL: https://issues.apache.org/jira/browse/TEZ-3625
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Priority: Minor
> Fix For: 0.9.0, 0.8.5
>
> Attachments: am_jstack, TEZ-3625.01.patch
>
>
> getVertex(String) does not obtain a readLock. It should, similar to getVertex(TezVertexId)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)