[
https://issues.apache.org/jira/browse/YARN-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated YARN-2171:
-----------------------------
Attachment: YARN-2171.patch
Patch to use AtomicInteger for the number of nodes so we can avoid grabbing the
lock to access the value. I also added a unit test to verify allocate doesn't
try to grab the capacity scheduler lock.
> AMs block on the CapacityScheduler lock during allocate()
> ---------------------------------------------------------
>
> Key: YARN-2171
> URL: https://issues.apache.org/jira/browse/YARN-2171
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 0.23.10, 2.4.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Critical
> Attachments: YARN-2171.patch
>
>
> When AMs heartbeat into the RM via the allocate() call they are blocking on
> the CapacityScheduler lock when trying to get the number of nodes in the
> cluster via getNumClusterNodes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
