[
https://issues.apache.org/jira/browse/YARN-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023020#comment-17023020
]
Gergely Pollak commented on YARN-9879:
--------------------------------------
As per our discussion with [~wilfreds], [~snemeth], [~sunilg], we will be
making the behaviour of the getQueuename configurable(by default the
getQueueName will return only the leaf name, but it can be changed to return
the full path), and will do the name changes as follows:
- External facing APIs will always use the getQueueName
- Internally we will use the full name to store / reference the queues, and we
will update the getQueueName method to getQueuePath, to make sure we are
working with fully qualified name
This way we minimize the impact for user, but both CS and migrating FS users
can use their external monitoring tools as they used to.
> Allow multiple leaf queues with the same name in CS
> ---------------------------------------------------
>
> Key: YARN-9879
> URL: https://issues.apache.org/jira/browse/YARN-9879
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Gergely Pollak
> Assignee: Gergely Pollak
> Priority: Major
> Attachments: DesignDoc_v1.pdf, YARN-9879.POC001.patch
>
>
> Currently the leaf queue's name must be unique regardless of its position in
> the queue hierarchy.
> Design doc and first proposal is being made, I'll attach it as soon as it's
> done.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
