[
https://issues.apache.org/jira/browse/YARN-10923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496658#comment-17496658
]
András Győri commented on YARN-10923:
-------------------------------------
h2. Dynamic Queue related methods
* setDynamicQueueProperties - it is also used by legacy AQC
* isInactiveDynmicQueue
* isDynamicQueue
h2. Analysis
* Difference between dynamic and static queues is the templating system, which
is located in setDynamicQueueProperties
* A queue can be converted to static queue, which would be harder in case
Dynamic Queues were extracted in to their own class
* This change would only be meaningful if legacy AQC and flexible AQC were
merged together, otherwise we would end up with two empty
> Investigate if creating separate classes for Dynamic Leaf / Dynamic Parent
> queues makes sense
> ---------------------------------------------------------------------------------------------
>
> Key: YARN-10923
> URL: https://issues.apache.org/jira/browse/YARN-10923
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Szilard Nemeth
> Assignee: András Győri
> Priority: Critical
>
> First, create 2 new classes: DynamicLeaf / DynamicParent.
> Then, gradually move AQC functionality from ManagedParentQueue /
> AutoCreatedLeafQueue.
> Revisit if AbstractManagedParentQueue makes sense at all.
> ManagedParent / Parent: Is there an actual need for the two classes?
> - Currently the two different parents can cause confusion and chaos
> - Can be a “back two the drawing board” task
> The ultimate goal is to have a common class for AQC-enabled parent and
> investigate if separate class for AutoCreatedLeafQueue is required.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
