[
https://issues.apache.org/jira/browse/YARN-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201884#comment-15201884
]
Sunil G commented on YARN-4839:
-------------------------------
I feel that a call to {{RMAppAttemptImpl.getMasterContainer }} is not very
clean or good from Scheduler side. I mentioned this point once in YARN-2005.
Its better we set that AM container is allocated via an Event to Scheduler or
via a direct api. But it comes with few lines of extra code. There were few
discussions on YARN-4143 for this. Will this be clean solution for this, so
that we can remove the dependency.
> 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)
