[ https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yufei Gu updated YARN-5077: --------------------------- Attachment: (was: YARN-5077.008.patch) > Fix FSLeafQueue#getFairShare() for queues with weight 0.0 > --------------------------------------------------------- > > Key: YARN-5077 > URL: https://issues.apache.org/jira/browse/YARN-5077 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Yufei Gu > Assignee: Yufei Gu > Attachments: YARN-5077.001.patch, YARN-5077.002.patch, > YARN-5077.003.patch, YARN-5077.004.patch, YARN-5077.005.patch, > YARN-5077.006.patch, YARN-5077.007.patch > > > 1) When a queue's weight is set to 0.0, FSLeafQueue#getFairShare() returns > <memory:0, vCores:0> > 2) When a queue's weight is nonzero, FSLeafQueue#getFairShare() returns > <memory:16384, vCores:8> > In case 1), that means no container ever gets allocated for an AM because > from the viewpoint of the RM, there is never any headroom to allocate a > container on that queue. > For example, we have a pool with the following weights: > - root.dev 0.0 > - root.product 1.0 > The root.dev is a best effort pool and should only get resources if > root.product is not running. In our tests, with no jobs running under > root.product, jobs started in root.dev queue stay stuck in ACCEPT phase and > never start. -- 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