[
https://issues.apache.org/jira/browse/YARN-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079588#comment-16079588
]
Hudson commented on YARN-6428:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11979 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11979/])
YARN-6428. Queue AM limit is not honored in CS always. Contributed by
(naganarasimha_gr: rev 626d730bfc4c1f6ea54e8a246a0a676cdb74937f)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/resource/DominantResourceCalculator.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java
> Queue AM limit is not honored in CS always
> -------------------------------------------
>
> Key: YARN-6428
> URL: https://issues.apache.org/jira/browse/YARN-6428
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bibin A Chundatt
> Assignee: Bibin A Chundatt
> Fix For: 3.0.0-beta1, 2.8.3, 2.9
>
> Attachments: YARN-6428.0001.patch, YARN-6428.0002.patch,
> YARN-6428.0003.patch, YARN-6428-branch-2.8.0003.patch
>
>
> Steps to reproduce
> ------------------------
> Setup cluster with 40 GB and 40 vcores with 4 Node managers with 10 GB each.
> Configure 100% to default queue as capacity and max am limit as 10 %
> Minimum scheduler memory and vcore as 512,1
> *Expected*
> AM limit 4096 and 4 vores
> *Actual*
> AM limit 4096+512 and 4+1 vcore
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
