[
https://issues.apache.org/jira/browse/TEZ-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121129#comment-14121129
]
Siddharth Seth commented on TEZ-1541:
-------------------------------------
The lock issue is inside the YARNs AMRMClientAsync.
When a TezSession is shutdown (tezClient.stop()) - it sets up handlers within
the AM for future shutdown, and returns.
After this. if the MiniCluster is shutdown, there's a possibility that the AM
is still talking to the RM to schedule resources. Once the RM goes down, this
invocation goes into a retry loop - while maintaining a lock, which is also
required to unregister from the RM (once this lock is obtained - this would be
another retry loop since the RM is no longer around).
> DAGAppMaster can get stuck on shutdown if the RM is no longer around
> --------------------------------------------------------------------
>
> Key: TEZ-1541
> URL: https://issues.apache.org/jira/browse/TEZ-1541
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Siddharth Seth
> Attachments: dagapp.threads.txt
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
