[jira] [Comment Edited] (YARN-8858) CapacityScheduler should respect maximum node resource when per-queue maximum-allocation is being used.

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

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

Wangda Tan edited comment on YARN-8858 at 10/9/18 5:39 AM:
-----------------------------------------------------------

[~cheersyang] / [~sunil.govind@gmail.com], can we get this patch committed to 3.2.0? -YARN-8720- introduced minor behavior change, we should fix it if possible.


was (Author: leftnoteasy):
[~cheersyang] / [~sunil.govind@gmail.com], can we get this patch committed to 3.2.0? It is a (minor) behavior change for YARN-8720.

> CapacityScheduler should respect maximum node resource when per-queue maximum-allocation is being used.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-8858
>                 URL: https://issues.apache.org/jira/browse/YARN-8858
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Sumana Sathish
>            Assignee: Wangda Tan
>            Priority: Critical
>         Attachments: YARN-8858.001.patch
>
>
> This issue happens after YARN-8720.
> Before that, AMS uses scheduler.getMaximumAllocation to do the normalization. After that, AMS uses LeafQueue.getMaximumAllocation. The scheduler one uses nodeTracker.getMaximumAllocation, but the LeafQueue.getMaximum doesn't. 
> We should use the scheduler.getMaximumAllocation to cap the per-queue's maximum-allocation every time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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