You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2016/03/25 19:30:25 UTC

[jira] [Resolved] (YARN-4839) ResourceManager deadlock between RMAppAttemptImpl and SchedulerApplicationAttempt

     [ https://issues.apache.org/jira/browse/YARN-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe resolved YARN-4839.
------------------------------
    Resolution: Duplicate

Resolving since the fix was incorporated into 2.8 as part of YARN-3361.

> 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)