[jira] [Commented] (YARN-1010) FairScheduler: decouple container scheduling from nodemanager heartbeats

["stefanlee (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YARN-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16283660#comment-16283660 ] 

stefanlee commented on YARN-1010:
---------------------------------

 Thanks [~ywskycn]   , i have a doubt that  if  _if (!completedContainers.isEmpty())_  will impact scheduler performance, why add this judgment here?


> FairScheduler: decouple container scheduling from nodemanager heartbeats
> ------------------------------------------------------------------------
>
>                 Key: YARN-1010
>                 URL: https://issues.apache.org/jira/browse/YARN-1010
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: scheduler
>    Affects Versions: 2.1.0-beta
>            Reporter: Alejandro Abdelnur
>            Assignee: Wei Yan
>            Priority: Critical
>             Fix For: 2.3.0
>
>         Attachments: YARN-1010.patch, YARN-1010.patch
>
>
> Currently scheduling for a node is done when a node heartbeats.
> For large cluster where the heartbeat interval is set to several seconds this delays scheduling of incoming allocations significantly.
> We could have a continuous loop scanning all nodes and doing scheduling. If there is availability AMs will get the allocation in the next heartbeat after the one that placed the request.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org