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 2015/02/04 20:07:34 UTC

[jira] [Created] (YARN-3137) CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock

Jason Lowe created YARN-3137:
--------------------------------

             Summary: CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock
                 Key: YARN-3137
                 URL: https://issues.apache.org/jira/browse/YARN-3137
             Project: Hadoop YARN
          Issue Type: Bug
    Affects Versions: 2.5.0
            Reporter: Jason Lowe


The queues are stored in a ConcurrentHashMap and the code already checks for a null queue.  At best we need to lock individual queues when processing the access check, but I don't see why we need to grab the highly-contested scheduler lock to lookup which queue to use for the hasAccess call.



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