[
https://issues.apache.org/jira/browse/YARN-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309974#comment-14309974
]
Wangda Tan commented on YARN-3153:
----------------------------------
We have 3 options basically,
1) Keep the config name (...percentage) and continue use it as ratio, add
additional checking for this to make sure it fit in range \[0,1\]
2) Keep the config name. Use it as percentage, this need update yarn-default as
well. This will have some impacts on existing deployments if they upgrade.
3) Change the config name to (...ratio), this will be a in-compatible change.
Thoughts? [~vinodkv], [~jianhe]
> 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)
