[
https://issues.apache.org/jira/browse/YARN-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201669#comment-15201669
]
Sangjin Lee commented on YARN-4839:
-----------------------------------
Could this be the same issue as pointed out by YARN-4247? We did see this issue
in our environment (which is 2.6 + patches), but that was because we backported
YARN-2005 without YARN-3361. Not sure if there has been a more recent
regression.
> ResourceManager deadlock between RMAppAttemptImpl and
> SchedulerApplicationAttempt
> ---------------------------------------------------------------------------------
>
> Key: YARN-4839
> URL: https://issues.apache.org/jira/browse/YARN-4839
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.8.0
> Reporter: Jason Lowe
> Priority: Blocker
>
> Hit a deadlock in the ResourceManager as one thread was holding the
> SchedulerApplicationAttempt lock and trying to call
> RMAppAttemptImpl.getMasterContainer while another thread had the
> RMAppAttemptImpl lock and was trying to call
> SchedulerApplicationAttempt.getResourceUsageReport.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
