[jira] [Resolved] (YARN-10923) Investigate if creating separate classes for Dynamic Leaf / Dynamic Parent queues makes sense

["András Győri (Jira)" <ji...@apache.org>]

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

András Győri resolved YARN-10923.
---------------------------------
    Resolution: Won't Fix

> 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: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org