[
https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299112#comment-15299112
]
Karthik Kambatla commented on YARN-5077:
----------------------------------------
In that case, should we update the way handleFixedShares addresses queues with
zero weight? May be, that method should include zero-weight queues in
nonFixedSchedulables that it constructs? That way, the helper method being
added in this patch doesn't have to recheck if the queue is active?
For the tests themselves, should we add a test to see that if a set minshare
for a queue with zero weight, it actually gets the minshare allocated?
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
