[
https://issues.apache.org/jira/browse/YARN-9950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16966415#comment-16966415
]
Prabhu Joseph commented on YARN-9950:
-------------------------------------
Thanks [~sunilg] for reviewing.
1. The below condition will prevent the case (1). The {{siblingQueues}} size
will be 1 only when a queue is added under a leaf queue.
*if (siblingQueues.size() == 1) {*
2. Yes it is not accurate, have changed the name to {{queueOrderingPolicy}} to
avoid confusion.
> Unset Ordering Policy of Leaf/Parent queue converted from Parent/Leaf queue
> respectively
> ----------------------------------------------------------------------------------------
>
> Key: YARN-9950
> URL: https://issues.apache.org/jira/browse/YARN-9950
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler
> Affects Versions: 3.3.0
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Major
> Attachments: YARN-9950-001.patch, YARN-9950-002.patch
>
>
> RM fails to start when adding a queue (say root.A.A1) under a leaf queue (say
> root.A) with ordering policy fifo.
> YARN supports fifo or fair for leaf queue and utilization or
> priority-utilization for parent queue. When the existing leaf queue (root.A)
> becomes parent queue - the ordering policy (fifo or fair) has to be unset.
> Else YARN RM will fail as fifo or fair is not a valid queue ordering policy
> for parent queue.
> Similarly while removing a queue, unset ordering policy of leaf queue which
> converted from parent queue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
