[ 
https://issues.apache.org/jira/browse/YARN-10386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171532#comment-17171532
 ] 

Peter Bacsko commented on YARN-10386:
-------------------------------------

Attached v1 version of the schema.

Explanation:
* {{type}}: user / group / application --- pretty much the first column of the 
current format.
* {{matches}}: it's either "\*" or a specific group/user -- the second column 
of the current format (will use "*" instead of "%user").
* {{policy}}: a fixed set of mapping policies, basically the same as an FS 
placement rule.
* {{queue}}: if the policy is {{user}}, {{primaryGroup}}, {{secondaryGroup}}, 
then this is prepended to the queue string. If the rule is {{defaultQueue}} 
then "root.default" will be overridden.
* {{nestedUserRule}}: optional, used only if {{nestedUser}} policy is defined. 
Note that unlike to Fair Scheduler, we don't have "outer" create flag, because 
it would require very deep changes in Capacity Scheduler. So we only support 
"innerCreate" for the "%user" part.
* {{fallbackResult}}: what happens if the placement fails, eg. the target queue 
does not exist or cannot be created. Right now in CS, we return "null" for the 
placement context which is interpreted as "root.default". In FS, we proceed to 
the next rule. Here, we can fine-tune this behavior: {{skip}} is the FS 
approach, {{placeDefault}} is the CS approach, {{reject}} is new and 
straightforward (submission will be rejected on the client side).
* {{defaultQueue}}: what should be the default queue in case of 
{{placeDefault}} fallback result.
* {{create}}: whether the queue should be created or not if it does not exist. 
Note that the parent queue of the leaf must be a managed parent in order for 
this switch to have effect. 


> Create new JSON schema for Placement Rules
> ------------------------------------------
>
>                 Key: YARN-10386
>                 URL: https://issues.apache.org/jira/browse/YARN-10386
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacity scheduler, capacityscheduler
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>         Attachments: MappingRulesDescription_v1.json
>
>
> Tasks in this JIRA:
>  # Create new JSON schema
>  # Add Maven plugin which generates Java POJOs based on the schema
>  # Add helper class which essentially does the same as #2 (for dev purposes)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to