hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3137) CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock
Date Wed, 04 Feb 2015 19:12:34 GMT

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

Wangda Tan commented on YARN-3137:
----------------------------------

Agree, I have noticed similar issues around this as well. Do you think YARN-3136/YARN-3137
should be tracked as sub-JIRA of YARN-3091?

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

Mime
View raw message