[
https://issues.apache.org/jira/browse/TEZ-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533847#comment-14533847
]
Jeff Zhang commented on TEZ-2421:
---------------------------------
[~bikassaha], I look at the jstack trace, not sure where's the deadlock. App
Shared Pool - #1 try to acquire VertexImpl's writelock and no other thread has
the writeblock except some thread also try to acquire the readlock. Would it
some resource contention issue. Maybe similar to TEZ-2269. And how to
reproduce it ?
> Deadlock in AM because attempt and vertex locking each other out
> ----------------------------------------------------------------
>
> Key: TEZ-2421
> URL: https://issues.apache.org/jira/browse/TEZ-2421
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Priority: Blocker
> Attachments: TEZ-2421.1.patch, TEZ-2421.2.patch, TEZ-2421.3.patch
>
>
> Ideally locks should be taken one way - either going down or up. Preferably
> not going up because most such data can be passed in during object
> construction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
