hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4047) ClientRMService getApplications has high scheduler lock contention
Date Fri, 14 Aug 2015 10:36:54 GMT

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

Hudson commented on YARN-4047:
------------------------------

FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #287 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/287/])
YARN-4047. ClientRMService getApplications has high scheduler lock contention. Contributed
by Jason Lowe (jianhe: rev 7a445fcfabcf9c6aae219051f65d3f6cb8feb87c)
* hadoop-yarn-project/CHANGES.txt
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ClientRMService.java


> ClientRMService getApplications has high scheduler lock contention
> ------------------------------------------------------------------
>
>                 Key: YARN-4047
>                 URL: https://issues.apache.org/jira/browse/YARN-4047
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>              Labels: 2.6.1-candidate
>             Fix For: 2.7.2
>
>         Attachments: YARN-4047.001.patch
>
>
> The getApplications call can be particuarly expensive because the code can call checkAccess
on every application being tracked by the RM.  checkAccess will often call scheduler.checkAccess
which will grab the big scheduler lock.  This can cause a lot of contention with the scheduler
thread which is busy trying to process node heartbeats, app allocation requests, etc.



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

Mime
View raw message