hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weiwei Yang (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-8858) CapacityScheduler should respect maximum node resource when per-queue maximum-allocation is being used.
Date Tue, 09 Oct 2018 06:26:00 GMT

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

Weiwei Yang edited comment on YARN-8858 at 10/9/18 6:25 AM:
------------------------------------------------------------

Patch looks good to me, pending on jenkins.


was (Author: cheersyang):
Patch looks good to me, pending on jenkins.

 

 

> 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


Mime
View raw message