[
https://issues.apache.org/jira/browse/YARN-9766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933372#comment-16933372
]
Sunil Govindan commented on YARN-9766:
--------------------------------------
[~tarunparimi] [~Prabhu Joseph]
I went through the fix. I think its a short term fix. And it may have impacts.
This should be fixed in more cleaner way. I would like to enforce this
validation if this doesnt make sense. Lets fix this at creation level of queues
itself.
# as per me, we are trying to over come the duplicated name issue by not
looking at old one
# this has happened because value got overriden.
Hence either we avoid such config, or reimplement the map to much better data
structure.
cc [~eepayne] [~leftnoteasy] [~cheersyang]
> YARN CapacityScheduler QueueMetrics has missing metrics for parent queues
> having same name
> ------------------------------------------------------------------------------------------
>
> Key: YARN-9766
> URL: https://issues.apache.org/jira/browse/YARN-9766
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Tarun Parimi
> Assignee: Tarun Parimi
> Priority: Major
> Attachments: YARN-9766.001.patch
>
>
> In Capacity Scheduler, we enforce Leaf Queues to have unique names. But it is
> not the case for Parent Queues. For example, we can have the below queue
> hierarchy, where "b" is the queue name for two different queue paths root.a.b
> and root.a.d.b . Since it is not a leaf queue this configuration works and
> apps run fine in the leaf queues 'c' and 'e'.
> * root
> ** a
> *** b
> **** c
> *** d
> **** b
> ***** e
> But the jmx metrics does not show the metrics for the parent queue
> "root.a.d.b" . We can see metrics only for "root.a.b" queue.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
