[YARN-3137] CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock - ASF JIRA

Add vote

Voters

Watch issue

Watchers

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Sub-task
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: 2.5.0
Fix Version/s: None
Component/s: None
Labels:
None

Description

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.