[ 
https://issues.apache.org/jira/browse/YARN-10599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko updated YARN-10599:
--------------------------------
    Description: 
The property 
{{yarn.scheduler.capacity.<queue-path>.auto-queue-creation-v2.enabled}} is not 
enabled by default for parent queues. However, users who migrate from FS need 
this property enabled for all parents, because FS allows all parents to have 
dynamic queues underneath them.

Note that this is only relevant if we convert directly to weights, it's not 
needed in percentage mode.

  was:The property 
{{yarn.scheduler.capacity.<queue-path>.auto-queue-creation-v2.enabled}} is not 
enabled by default for parent queues. However, users who migrate from FS need 
this property enabled for all parents, because FS allows all parents to have 
dynamic queues underneath them.


> fs2cs should generate new "auto-queue-creation-v2.enabled" properties for all 
> parents
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-10599
>                 URL: https://issues.apache.org/jira/browse/YARN-10599
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>              Labels: fs2cs
>
> The property 
> {{yarn.scheduler.capacity.<queue-path>.auto-queue-creation-v2.enabled}} is 
> not enabled by default for parent queues. However, users who migrate from FS 
> need this property enabled for all parents, because FS allows all parents to 
> have dynamic queues underneath them.
> Note that this is only relevant if we convert directly to weights, it's not 
> needed in percentage mode.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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