You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2015/02/04 19:58:34 UTC

[jira] [Created] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

Jason Lowe created YARN-3136:
--------------------------------

             Summary: 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: Bug
          Components: scheduler
    Affects Versions: 2.6.0
            Reporter: Jason Lowe


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)