[
https://issues.apache.org/jira/browse/YARN-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271355#comment-17271355
]
Peter Bacsko edited comment on YARN-10596 at 1/25/21, 3:04 PM:
---------------------------------------------------------------
Ok, I've just read this sentence:
_Since it is not an edge case, we also need to support the creation of a
ParentQueue instead of a LeafQueue, if auto-queue-creation-v2 is enabled, even
when no child queue is defined under the parent._
My understanding was that by default, all parents are allowed of having dynamic
queues created. If this is not true, that means:
1. If someone wants all parents to have dynamic queues (which is standard for
FS users who are migrating), then this property must be set for all parents.
2. This affects fs2cs tool, because it does not set "auto-queue-creation-v2"
at all.
I pointed this out in my comment
https://issues.apache.org/jira/browse/YARN-10506?focusedCommentId=17264903&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17264903.
See paragraph which begins with "We also have to think about the following
scenario" and conclusion point #2.
was (Author: pbacsko):
Ok, I've just read this sentence:
_Since it is not an edge case, we also need to support the creation of a
ParentQueue instead of a LeafQueue, if auto-queue-creation-v2 is enabled, even
when no child queue is defined under the parent._
My understanding was that by default, all parents are allowed of having dynamic
queues created. If this is not true, that means:
1. If someone wants all parents to have dynamic queues (which is standard for
FS users who are migrating), then this property must be set for all parents.
2. This affects fs2cs tool, because it does not set "auto-queue-creation-v2" at
all.
I pointed this out in my comment
https://issues.apache.org/jira/browse/YARN-10506?focusedCommentId=17264903&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17264903.
See paragraph which begins with "We also have to think about the following
scenario" and conclusion point #2.
> Allow static definition of childless ParentQueues with auto-queue-creation-v2
> enabled
> -------------------------------------------------------------------------------------
>
> Key: YARN-10596
> URL: https://issues.apache.org/jira/browse/YARN-10596
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Andras Gyori
> Assignee: Andras Gyori
> Priority: Major
> Attachments: YARN-10596.001.patch
>
>
> The old auto queue creation/managed queue logic allowed the definition of
> childless parents to be created statically, if the auto-create-child-queue
> flag was turned on the parent (thus making it a ManagedParentQueue).
> Since it is not an edge case, we also need to support the creation of a
> ParentQueue instead of a LeafQueue, if auto-queue-creation-v2 is enabled,
> even when no child queue is defined under the parent.
--
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
