[
https://issues.apache.org/jira/browse/YARN-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310023#comment-14310023
]
Jian He commented on YARN-3153:
-------------------------------
As the
[doc|http://hadoop.apache.org/docs/r2.3.0/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
already explicitly mentions "specified as float", to keep it compatible, we
may choose to do 1)
> Capacity Scheduler max AM resource limit for queues is defined as percentage
> but used as ratio
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-3153
> URL: https://issues.apache.org/jira/browse/YARN-3153
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Critical
>
> In existing Capacity Scheduler, it can limit max applications running within
> a queue. The config is yarn.scheduler.capacity.maximum-am-resource-percent,
> but actually, it is used as "ratio", in implementation, it assumes input will
> be \[0,1\]. So now user can specify it up to 100, which makes AM can use 100x
> of queue capacity. We should fix that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
