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

Sunil G commented on YARN-4003:
-------------------------------

HI [~curino] [~leftnoteasy]
Sorry for coming in this late. 
As given in above example, we are trying to get applications started for R3 
opportunistically. And with this given patch, we have now more bandwidth and 
app can be submitted. Also to resolve more AMs taken over cluster case, If i 
understood correctly we plan for a max-am-percent. But this factor will be 
calculated per ParentQueue absolutely capacity, correct? And if all child 
queues are using this, and assume i gave max as .5, we may end up in having 
more than .5 for AM containers as all childqueues are thinking it can run .5 of 
parent?. pls correct me if I am wrong.


> ReservationQueue inherit getAMResourceLimit() from LeafQueue, but behavior is 
> not consistent
> --------------------------------------------------------------------------------------------
>
>                 Key: YARN-4003
>                 URL: https://issues.apache.org/jira/browse/YARN-4003
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Carlo Curino
>            Assignee: Carlo Curino
>         Attachments: YARN-4003.patch
>
>
> The inherited behavior from LeafQueue (limit AM % based on capacity) is not a 
> good fit for ReservationQueue (that have highly dynamic capacity). 



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

Reply via email to