[jira] [Updated] (YARN-10620) fs2cs: parentQueue for certain placement rules are not set during conversion

["Peter Bacsko (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Bacsko updated YARN-10620:
--------------------------------
    Description: 
There are some placement rules in FS which are currently not handled properly by fs2cs:

{noformat}
<queuePlacementPolicy>
        <rule name="user" create="true"/>
        <rule name="primaryGroup" create="true"/>
    </queuePlacementPolicy>
{noformat}

The first rule means that if the user queue doesn't exist, it should be created as {{root.<user>}}.
The second means the same thing, except refers to the primary group instead of the submitting user: {{root.<primaryGroup>}}.

The problem is that in order for the create="true" setting to take effect, we must set the parent queue in the generated JSON:

{noformat}
{
  "rules" : [ {
    "type" : "user",
    "matches" : "*",
    "policy" : "user",
    "fallbackResult" : "skip",
    "create" : true
  }, {
    "type" : "user",
    "matches" : "*",
    "policy" : "primaryGroup",
    "fallbackResult" : "skip",
    "create" : true
  } ]
}
{noformat}

This is missing right now and it need to be fixed.

> fs2cs: parentQueue for certain placement rules are not set during conversion
> ----------------------------------------------------------------------------
>
>                 Key: YARN-10620
>                 URL: https://issues.apache.org/jira/browse/YARN-10620
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>              Labels: fs2cs
>
> There are some placement rules in FS which are currently not handled properly by fs2cs:
> {noformat}
> <queuePlacementPolicy>
>         <rule name="user" create="true"/>
>         <rule name="primaryGroup" create="true"/>
>     </queuePlacementPolicy>
> {noformat}
> The first rule means that if the user queue doesn't exist, it should be created as {{root.<user>}}.
> The second means the same thing, except refers to the primary group instead of the submitting user: {{root.<primaryGroup>}}.
> The problem is that in order for the create="true" setting to take effect, we must set the parent queue in the generated JSON:
> {noformat}
> {
>   "rules" : [ {
>     "type" : "user",
>     "matches" : "*",
>     "policy" : "user",
>     "fallbackResult" : "skip",
>     "create" : true
>   }, {
>     "type" : "user",
>     "matches" : "*",
>     "policy" : "primaryGroup",
>     "fallbackResult" : "skip",
>     "create" : true
>   } ]
> }
> {noformat}
> This is missing right now and it need to be fixed.



--
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