hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6428) Queue AM limit is not honored in CS always
Date Sat, 24 Jun 2017 18:13:01 GMT

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

Naganarasimha G R commented on YARN-6428:
-----------------------------------------

[~sunilg] & [~wangda],
   Current API is mostly used by passing float parameter except for the {{TempQueuePerPartition.normalizedGuarantee}},
where in here too we could have used float but its just that its been set to double. So for
all current usages i feel the existing patch is good considering that {{TempQueuePerPartition.normalizedGuarantee}}
is corrected to float. Thoughts ?

> 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
>         Attachments: YARN-6428.0001.patch, YARN-6428.0002.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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message