[
https://issues.apache.org/jira/browse/YARN-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153815#comment-16153815
]
Esther Zheng commented on YARN-6686:
------------------------------------
[~jhung] Thanks for your information.
Here is my proposal of fixing the issue mentioned above. Can we have getParams
and updateParams as follows? The updateParams has a pair of from and to values,
so that the value cannot be updated if the current value doesn't match the from
value. This way we can prevent the undesired results from attempting to update
the values simultaneously. Any comments?
{code:java}
<global-updates>
<getParams>
<entry>
<key>yarn.scheduler.capacity.queue-mappings</key>
<value>u:user1:queue1,u:%user:%user</value>
</entry>
</getParams>
</global-updates>
{code}
{code:java}
<global-updates>
<updateParams>
<entry>
<key>yarn.scheduler.capacity.queue-mappings</key>
<value>
<to>u:user1:queue2,u:%user:%user</to>
<from>u:user1:queue1,u:%user:%user</from>
</value>
</entry>
</updateParams>
</global-updates>
{code}
> 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
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
