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 "Hudson (JIRA)" <ji...@apache.org> on 2015/04/18 02:33:59 UTC

[jira] [Commented] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue

    [ https://issues.apache.org/jira/browse/YARN-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500954#comment-14500954 ] 

Hudson commented on YARN-3487:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #7610 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/7610/])
YARN-3487. CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue (Jason Lowe via wangda) (wangda: rev f47a5763acd55cb0b3f16152c7f8df06ec0e09a9)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
* hadoop-yarn-project/CHANGES.txt


> CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue
> -----------------------------------------------------------------------------
>
>                 Key: YARN-3487
>                 URL: https://issues.apache.org/jira/browse/YARN-3487
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>    Affects Versions: 2.6.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Critical
>             Fix For: 2.7.1
>
>         Attachments: YARN-3487.001.patch, YARN-3487.002.patch, YARN-3487.003.patch
>
>
> Recently saw a significant slowdown of applications on a large cluster, and we noticed there were a large number of blocked threads on the RM.  Most of the blocked threads were waiting for the CapacityScheduler lock while calling getQueueInfo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)