[
https://issues.apache.org/jira/browse/TEZ-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533734#comment-14533734
]
Bikas Saha commented on TEZ-2421:
---------------------------------
The main issue is that the attempt takes a lock upwards into the vertex while
vertex takes locks downwards into the attempt. One way has to be broken to
prevent deadlock. The key culprits are getting the remoteTaskSpec and getting
the taskLocation.
Instead of the attempt up-calling into the vertex to get these after getting
scheduled, the vertex is now sending these to the task when it schedules the
task. [~zjffdu] [~sseth] [~hitesh] Please review.
> 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
> Attachments: TEZ-2421.1.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)
