You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Anthony Hsu (JIRA)" <ji...@apache.org> on 2019/02/14 22:18:00 UTC
[jira] [Commented] (YARN-6686) Support for adding and removing
queue mappings
[ https://issues.apache.org/jira/browse/YARN-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16768763#comment-16768763 ]
Anthony Hsu commented on YARN-6686:
-----------------------------------
Hi [~csexz],
I like your proposal of using <from> and <to>. I have one suggestion. Instead of having separate <getParams> and <updateParams>, I think everything should be an <updateParams> (<getParams> to me sounds like it's a read-only request, not an update request).
* If <value> just contains text, then it's a complete replacement.
* If <value> has <from> and <to> children, then it's an addition, removal, or update
||Operation|| <from>||<to>||Description/Notes||
|Addition|(empty)|u:<user1>:<queue1>,u:<user2>:<queue2>,...|Adds the mappings u:<user1>:<queue1>,u:<user2>:<queue2>,... |
|Removal|u:<user1>:<queue1>,u:<user2>:<queue2>,...|(empty)|Removes the mappings u:<user1>:<queue1>,u:<user2>:<queue2>,...|
|Update|u:<user1>:<queue1>,u:<user2>:<queue2>,...|u:<user1>:<queue1'>,u:<user2>:<queue2'>,...|Updates the mappings for users <user1>, <user2>, ... from <queue1>, <queue2>, ... to <queue1'>, <queue2'>, ...
The <from> and <to> should contain the same number of items.|
> Support for adding and removing queue mappings
> ----------------------------------------------
>
> Key: YARN-6686
> URL: https://issues.apache.org/jira/browse/YARN-6686
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Jonathan Hung
> Assignee: Jonathan Hung
> Priority: Major
> Attachments: YARN-6686-YARN-5734.001.patch
>
>
> Right now capacity scheduler uses UserGroupMappingPlacementRule to determine queue mappings. This rule stores mappings in {{yarn.scheduler.capacity.queue-mappings}}. For users with a large number of mappings, adding or removing queue mappings becomes infeasible.
> Need to come up with a way to add/remove individual mappings, for any/all different configured placement rules.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org