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

Aihua Xu commented on YARN-9116:
--------------------------------

Thanks [~leftnoteasy]. I will look into what you mentioned above. Sounds like a 
good implementation to handle different resource types. Originally I was only 
thinking of memory and vCores.

[~cheersyang] What I'm trying to achieve is to configure a larger container 
queue. To my understanding from the implementation of YARN-1582, we have to do 
the following steps:
# Configure the global maximum-allocation to 120G/256vCores
# Configure regular queues to 16G/16vCores or desired values
# Configure larger container queue to 120G/256vCores

The default queue-default I'm talking about is just to set to 16G/16vCores in 
this case. Without such default value, you have to set for all the queues. This 
is just the default value and you can set the desired one if the queue need a 
different value. 



> Capacity Scheduler: add the default maximum-allocation-mb and 
> maximum-allocation-vcores for the queues
> ------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-9116
>                 URL: https://issues.apache.org/jira/browse/YARN-9116
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacity scheduler
>    Affects Versions: 2.7.0
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>            Priority: Major
>
> YARN-1582 adds the support of maximum-allocation-mb configuration per queue 
> which is targeting to support larger container features on dedicated queues 
> (larger maximum-allocation-mb/maximum-allocation-vcores for such queue) . 
> While to achieve larger container configuration, we need to increase the 
> global maximum-allocation-mb/maximum-allocation-vcores (e.g. 120G/256) and 
> then override those configurations with desired values on the queues since 
> queue configuration can't be larger than cluster configuration. There are 
> many queues in the system and if we forget to configure such values when 
> adding a new queue, then such queue gets default 120G/256 which typically is 
> not what we want.  
> We can come up with a queue-default configuration (set to normal queue 
> configuration like 16G/8), so the leaf queues gets such values by default.



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

Reply via email to