hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil Govindan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-8858) CapacityScheduler should respect maximum node resource when per-queue maximum-allocation is being used.
Date Mon, 15 Oct 2018 10:12:01 GMT

     [ https://issues.apache.org/jira/browse/YARN-8858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sunil Govindan updated YARN-8858:
---------------------------------
    Priority: Major  (was: Critical)

> 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: Major
>             Fix For: 2.10.0, 3.2.0, 2.9.2, 3.0.4, 3.1.2, 3.3.0
>
>         Attachments: YARN-8858-branch-2.8.001.patch, YARN-8858.001.patch, YARN-8858.002.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