[
https://issues.apache.org/jira/browse/YARN-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380029#comment-16380029
]
Sunil G commented on YARN-3153:
-------------------------------
[~maniraj...@gmail.com]
Since we are looking for a deprecation of
{{yarn.scheduler.capacity.maximum-am-resource-percent}} and introduce something
like {{yarn.scheduler.capacity.maximum-am-capacity}}
I think we have to support both for some more time, 3.0 was a correct version
for this to deprecate. So now we can look ahead and try to fix this in next
major version (but have old one for some more version for compatibility issue)
I think "default per cluster + override per queue is sufficient." model may be
better. This means that all queues will use whats set in cluster level. Each
queue can override as needed, I am not seeing inheritance from parent queue is
very much needed here. cc [~leftnoteasy]
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
