[ https://issues.apache.org/jira/browse/YARN-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782429#comment-13782429 ]
Hadoop QA commented on YARN-1010: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12605994/YARN-1010.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 2 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/2046//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2046//console This message is automatically generated. > 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 > Attachments: 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.1#6144)