[
https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14501982#comment-14501982
]
Hudson commented on YARN-3136:
------------------------------
SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2118 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2118/])
YARN-3136. Fixed a synchronization problem of
AbstractYarnScheduler#getTransferredContainers. Contributed by Sunil G (jianhe:
rev 497c86b485b1bb8a2eba52308646d8e1ee76bce3)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/AbstractYarnScheduler.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ApplicationMasterService.java
* hadoop-yarn-project/hadoop-yarn/dev-support/findbugs-exclude.xml
* hadoop-yarn-project/CHANGES.txt
> getTransferredContainers can be a bottleneck during AM registration
> -------------------------------------------------------------------
>
> Key: YARN-3136
> URL: https://issues.apache.org/jira/browse/YARN-3136
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: scheduler
> Affects Versions: 2.6.0
> Reporter: Jason Lowe
> Assignee: Sunil G
> Fix For: 2.8.0
>
> Attachments: 0001-YARN-3136.patch, 00010-YARN-3136.patch,
> 00011-YARN-3136.patch, 00012-YARN-3136.patch, 00013-YARN-3136.patch,
> 0002-YARN-3136.patch, 0003-YARN-3136.patch, 0004-YARN-3136.patch,
> 0005-YARN-3136.patch, 0006-YARN-3136.patch, 0007-YARN-3136.patch,
> 0008-YARN-3136.patch, 0009-YARN-3136.patch
>
>
> While examining RM stack traces on a busy cluster I noticed a pattern of AMs
> stuck waiting for the scheduler lock trying to call getTransferredContainers.
> The scheduler lock is highly contended, especially on a large cluster with
> many nodes heartbeating, and it would be nice if we could find a way to
> eliminate the need to grab this lock during this call. We've already done
> similar work during AM allocate calls to make sure they don't needlessly grab
> the scheduler lock, and it would be good to do so here as well, if possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
