[
https://issues.apache.org/jira/browse/YARN-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020351#comment-17020351
]
Gergely Pollak commented on YARN-9879:
--------------------------------------
Uploaded the firs POC patch. This version CAN run jobs by their short AND their
full name, currently the leaf uniqueness constraint is in place, but the data
store it prepared for leaf collisions. Currently working on testing and if
nothing seems to be broken, I can remove the uniqueness constraint from leaf
queues. Also I can add the feature control flag, as discussed earlier.
The biggest risk I see is the modification in AbstractCSQueue where I've
changed the getQueueName to return the full name of the queue. Based on my
analysis this method is mostly called to get the queue's string identifier, and
as it was mentioned earlier we should use full queue names for queue
identification. So I need to carefully check every call of this method if it
breaks anything. But a quick smoke test was successful, I was able to start a
job using only the leaf queue name as well as using the full queue name.
> 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]
