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 "Peter Bacsko (Jira)" <ji...@apache.org> on 2020/11/10 12:55:00 UTC
[jira] [Commented] (YARN-10103) Capacity scheduler: add support for
create=true/false per mapping rule
[ https://issues.apache.org/jira/browse/YARN-10103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229191#comment-17229191 ]
Peter Bacsko commented on YARN-10103:
-------------------------------------
I'm about to close this Jira for the following reasons:
1) "create" will be introduced in the new placement engine (YARN-10370). Let's leave the existing codebase and format alone which is already hard to read.
2) We will come up with a new approach to create dynamic queues anywhere, pretty much like in FS. Not sure if there's an upstream ticket yet, but soon we'll create one.
cc [~snemeth]
> Capacity scheduler: add support for create=true/false per mapping rule
> ----------------------------------------------------------------------
>
> Key: YARN-10103
> URL: https://issues.apache.org/jira/browse/YARN-10103
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Peter Bacsko
> Priority: Major
> Labels: fs2cs
>
> You can't ask Capacity Scheduler for a mapping to create a queue if it doesn't exist.
> For example, this mapping would use the first rule if the queue exist. If it doesn't, then it proceeds to the next rule:
> {{u:%user:%primary_group.%user:create=false;u:%user%:root.default}}
> Let's say user "alice" belongs to the "admins" group. It would first try to map {{root.admins.alice}}. But, if the queue doesn't exist, then it places the application into {{root.default}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org