[
https://issues.apache.org/jira/browse/YARN-9772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957934#comment-16957934
]
Prabhu Joseph edited comment on YARN-9772 at 10/23/19 2:53 PM:
---------------------------------------------------------------
Full Queue Path Support is required to allow queues to share the same name.
This will help customers with FS to migrate easily (YARN-7621).
Full Queue Path Support needs lot of effort and also it should not affect the
existing behavior like the way queue name specified in Yarn Application and
Capacity Scheduler Configs (Queues, Queue Placement mapping).
Until this gets fixed, will suggest to have an immediate fix by not allowing
queues to share same name to solve the existing inconsistent behavior.
(YARN-9772, YARN-9925, YARN-9766). If you are okay, have a
[patch|https://issues.apache.org/jira/secure/attachment/12983845/YARN-9925-003.patch]
to disallow such queues which can be used.
was (Author: prabhu joseph):
Full Queue Path Support is required to allow queues to share the same name.
This will help customers with FS to migrate easily (YARN-7621).
Full Queue Path Support needs lot of effort and also it should not affect the
existing behavior like the way queue name specified in Yarn Application and
Capacity Scheduler Configs (Queues, Queue Placement mapping).
Until this gets fixed, will suggest to have an immediate fix by not allowing
queues to share same name to solve the existing inconsistent behavior.
(YARN-9772, YARN-9925, YARN-9766). If you are okay, have a
[^YARN-9925-003.patch] to disallow such queues which can be used.
> CapacitySchedulerQueueManager has incorrect list of queues
> ----------------------------------------------------------
>
> Key: YARN-9772
> URL: https://issues.apache.org/jira/browse/YARN-9772
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
>
> CapacitySchedulerQueueManager has incorrect list of queues when there is more
> than one parent queue (say at middle level) with same name.
> For example,
> * root
> ** a
> *** b
> **** c
> *** d
> **** b
> ***** e
> {{CapacitySchedulerQueueManager#getQueues}} maintains these list of queues.
> While parsing "root.a.d.b", it overrides "root.a.b" with new Queue object in
> the map because of similar name. After parsing all the queues, map count
> should be 7, but it is 6. Any reference to queue "root.a.b" in code path is
> nothing but "root.a.d.b" object. Since
> {{CapacitySchedulerQueueManager#getQueues}} has been used in multiple places,
> will need to understand the implications in detail. For example,
> {{CapapcityScheduler#getQueue}} has been used in many places which in turn
> uses {{CapacitySchedulerQueueManager#getQueues}}. cc [~eepayne], [~sunilg]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
