hadoop-yarn-issues mailing list archives

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

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

Vinod Kumar Vavilapalli commented on YARN-3137:
-----------------------------------------------

bq. 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.
Queue hierarchy may change at any point of time due to refreshQueues. We need a way to lock
the queue-hierarchy itself.

> CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock
> --------------------------------------------------------------------
>
>                 Key: YARN-3137
>                 URL: https://issues.apache.org/jira/browse/YARN-3137
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 2.5.0
>            Reporter: Jason Lowe
>            Assignee: Varun Saxena
>
> 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