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

Wangda Tan commented on YARN-3153:
----------------------------------

Thanks for your feedbacks, I agree to do 1) first. I think 
deprecating+change-name is not so graceful enough, user will get confused when 
he found one option deprecated but system suggest to use a very similar one.

Will upload a patch for #1 shortly.

> 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)

Reply via email to