[
https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363845#comment-14363845
]
Jason Lowe commented on YARN-3136:
----------------------------------
Thanks for updating the patch, Sunil. Two of the findbug warnings appear to be
linked to this patch, specifically these:
{noformat}
<BugInstance type='IS2_INCONSISTENT_SYNC' priority='Normal'
category='MT_CORRECTNESS' message='Inconsistent synchronization of
org.apache.hadoop.yarn.server.resourcemanager.scheduler.AbstractYarnScheduler.applications;
locked 90% of time' lineNumber='138'/>
<BugInstance type='IS2_INCONSISTENT_SYNC' priority='Normal'
category='MT_CORRECTNESS' message='Inconsistent synchronization of
org.apache.hadoop.yarn.server.resourcemanager.scheduler.AbstractYarnScheduler.rmContext;
locked 95% of time' lineNumber='140'/>
{noformat}
> 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
> Attachments: 0001-YARN-3136.patch, 0002-YARN-3136.patch,
> 0003-YARN-3136.patch, 0004-YARN-3136.patch, 0005-YARN-3136.patch,
> 0006-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)
