[ https://issues.apache.org/jira/browse/YARN-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301562#comment-15301562 ]
Hudson commented on YARN-4866: ------------------------------ SUCCESS: Integrated in Hadoop-trunk-Commit #9864 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/9864/]) YARN-4866. FairScheduler: AMs can consume all vcores leading to a (kasha: rev 4f513a4a8ed73beec89b7b28c0cd056ee5f4ed0d) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSLeafQueue.java > FairScheduler: AMs can consume all vcores leading to a livelock when using > FAIR policy > -------------------------------------------------------------------------------------- > > Key: YARN-4866 > URL: https://issues.apache.org/jira/browse/YARN-4866 > Project: Hadoop YARN > Issue Type: Bug > Components: fairscheduler > Affects Versions: 2.8.0 > Reporter: Karthik Kambatla > Assignee: Yufei Gu > Attachments: YARN-4866.001.patch, YARN-4866.002.patch, > YARN-4866.003.patch, YARN-4866.004.patch, YARN-4866.005.patch, > YARN-4866.006.patch, YARN-4866.007.patch, YARN-4866.008.patch, > YARN-4866.009.patch > > > The maxAMShare uses the queue's policy for enforcing limits. When using FAIR > policy, this considers only memory. If there are fewer vcores on the cluster, > the AMs can end up taking all the vcores leading to a livelock. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org