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

Manikandan R updated YARN-9772:
-------------------------------
    Description: 
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]

  was:
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] }}


> 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.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to