[
https://issues.apache.org/jira/browse/YARN-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated YARN-3487:
-----------------------------
Attachment: YARN-3487.003.patch
Thanks for the feedback, Wangda and Sunil. In the interest of keeping this
JIRA simple to expedite the getQueueInfo and getQueue fix this version of the
patch restores the lock on checkAccess. IIRC there's already another JIRA
proposing to add read/write locks to the CapacityScheduler to handle rare
events like queue config refresh.
> CapacityScheduler scheduler lock obtained unnecessarily
> -------------------------------------------------------
>
> Key: YARN-3487
> URL: https://issues.apache.org/jira/browse/YARN-3487
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 2.6.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Critical
> Attachments: YARN-3487.001.patch, YARN-3487.002.patch,
> YARN-3487.003.patch
>
>
> Recently saw a significant slowdown of applications on a large cluster, and
> we noticed there were a large number of blocked threads on the RM. Most of
> the blocked threads were waiting for the CapacityScheduler lock while calling
> getQueueInfo.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
