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

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

Hi [~sunilg] & [~leftnoteasy],
This issue is very critical for our usecase where in we use cluster by having 2 
partitions (non DEFAULT_PARTITION s). So if the Max-AM-Resource-Percentage is 
calculated based on DEFAULT_PARTITION size then it practically limits to only 
one app being submitted. 
Also i feel even though its hard for debugging its better to opt for approach 2 
as we can clearly specify AMResourceLimit for each partition and further we are 
having some jira's YARN-3946 which try to indicate the reasons for Application 
not being launched. Thoughts ?


> Max-AM-Resource-Percentage should respect node labels
> -----------------------------------------------------
>
>                 Key: YARN-3216
>                 URL: https://issues.apache.org/jira/browse/YARN-3216
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Sunil G
>            Priority: Critical
>         Attachments: 0001-YARN-3216.patch
>
>
> Currently, max-am-resource-percentage considers default_partition only. When 
> a queue can access multiple partitions, we should be able to compute 
> max-am-resource-percentage based on that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to