[jira] [Updated] (YARN-10620) fs2cs: parentQueue for certain placement rules are not set during conversion
[
https://issues.apache.org/jira/browse/YARN-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated YARN-10620:
--
Component/s: capacity scheduler
Target Version/s: 3.4.0
Affects Version/s: 3.4.0
> 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
> Components: capacity scheduler
>Affects Versions: 3.4.0
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Labels: fs2cs
> Fix For: 3.4.0
>
> Attachments: YARN-10620-001.patch, YARN-10620-002.patch
>
>
> There are some placement rules in FS which are currently not handled properly
> by fs2cs:
> {noformat}
>
>
>
>
> {noformat}
> The first rule means that if the user queue doesn't exist, it should be
> created as {{root.}}.
> The second means the same thing, except refers to the primary group instead
> of the submitting user: {{root.}}.
> The problem is that in order for the create="true" setting to take effect, we
> must set the parent queue in the generated JSON:
> Current:
> {noformat}
> {
> "rules" : [ {
> "type" : "user",
> "matches" : "*",
> "policy" : "user",
> "fallbackResult" : "skip",
> "create" : true
> }, {
> "type" : "user",
> "matches" : "*",
> "policy" : "primaryGroup",
> "fallbackResult" : "skip",
> "create" : true
> } ]
> }
> {noformat}
> Expected:
> {noformat}
> {
> "rules" : [ {
> "type" : "user",
> "matches" : "*",
> "policy" : "user",
> "fallbackResult" : "skip",
> "parentQueue": "root",
> "create" : true
> }, {
> "type" : "user",
> "matches" : "*",
> "policy" : "primaryGroup",
> "fallbackResult" : "skip",
> "parentQueue": "root",
> "create" : true
> } ]
> {noformat}
> This is missing right now and it need to be fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10620) fs2cs: parentQueue for certain placement rules are not set during conversion
[
https://issues.apache.org/jira/browse/YARN-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Szilard Nemeth updated YARN-10620:
--
Fix Version/s: 3.4.0
> 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
> Fix For: 3.4.0
>
> Attachments: YARN-10620-001.patch, YARN-10620-002.patch
>
>
> There are some placement rules in FS which are currently not handled properly
> by fs2cs:
> {noformat}
>
>
>
>
> {noformat}
> The first rule means that if the user queue doesn't exist, it should be
> created as {{root.}}.
> The second means the same thing, except refers to the primary group instead
> of the submitting user: {{root.}}.
> The problem is that in order for the create="true" setting to take effect, we
> must set the parent queue in the generated JSON:
> Current:
> {noformat}
> {
> "rules" : [ {
> "type" : "user",
> "matches" : "*",
> "policy" : "user",
> "fallbackResult" : "skip",
> "create" : true
> }, {
> "type" : "user",
> "matches" : "*",
> "policy" : "primaryGroup",
> "fallbackResult" : "skip",
> "create" : true
> } ]
> }
> {noformat}
> Expected:
> {noformat}
> {
> "rules" : [ {
> "type" : "user",
> "matches" : "*",
> "policy" : "user",
> "fallbackResult" : "skip",
> "parentQueue": "root",
> "create" : true
> }, {
> "type" : "user",
> "matches" : "*",
> "policy" : "primaryGroup",
> "fallbackResult" : "skip",
> "parentQueue": "root",
> "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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10620) fs2cs: parentQueue for certain placement rules are not set during conversion
[
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}
{noformat}
The first rule means that if the user queue doesn't exist, it should be created
as {{root.}}.
The second means the same thing, except refers to the primary group instead of
the submitting user: {{root.}}.
The problem is that in order for the create="true" setting to take effect, we
must set the parent queue in the generated JSON:
Current:
{noformat}
{
"rules" : [ {
"type" : "user",
"matches" : "*",
"policy" : "user",
"fallbackResult" : "skip",
"create" : true
}, {
"type" : "user",
"matches" : "*",
"policy" : "primaryGroup",
"fallbackResult" : "skip",
"create" : true
} ]
}
{noformat}
Expected:
{noformat}
{
"rules" : [ {
"type" : "user",
"matches" : "*",
"policy" : "user",
"fallbackResult" : "skip",
"parentQueue": "root",
"create" : true
}, {
"type" : "user",
"matches" : "*",
"policy" : "primaryGroup",
"fallbackResult" : "skip",
"parentQueue": "root",
"create" : true
} ]
{noformat}
This is missing right now and it need to be fixed.
was:
There are some placement rules in FS which are currently not handled properly
by fs2cs:
{noformat}
{noformat}
The first rule means that if the user queue doesn't exist, it should be created
as {{root.}}.
The second means the same thing, except refers to the primary group instead of
the submitting user: {{root.}}.
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
> Attachments: YARN-10620-001.patch, YARN-10620-002.patch
>
>
> There are some placement rules in FS which are currently not handled properly
> by fs2cs:
> {noformat}
>
>
>
>
> {noformat}
> The first rule means that if the user queue doesn't exist, it should be
> created as {{root.}}.
> The second means the same thing, except refers to the primary group instead
> of the submitting user: {{root.}}.
> The problem is that in order for the create="true" setting to take effect, we
> must set the parent queue in the generated JSON:
> Current:
> {noformat}
> {
> "rules" : [ {
> "type" : "user",
> "matches" : "*",
> "policy" : "user",
> "fallbackResult" : "skip",
> "create" : true
> }, {
> "type" : "user",
> "matches" : "*",
> "policy" : "primaryGroup",
> "fallbackResult" : "skip",
> "create" : true
> } ]
> }
> {noformat}
> Expected:
> {noformat}
> {
> "rules" : [ {
> "type" : "user",
> "matches" : "*",
> "policy" : "user",
> "fallbackResult" : "skip",
> "parentQueue": "root",
> "create" : true
> }, {
> "type" : "user",
> "matches" : "*",
> "policy" : "primaryGroup",
> "fallbackResult" : "skip",
> "parentQueue": "root",
> "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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10620) fs2cs: parentQueue for certain placement rules are not set during conversion
[
https://issues.apache.org/jira/browse/YARN-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko updated YARN-10620:
Attachment: YARN-10620-002.patch
> 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
> Attachments: YARN-10620-001.patch, YARN-10620-002.patch
>
>
> There are some placement rules in FS which are currently not handled properly
> by fs2cs:
> {noformat}
>
>
>
>
> {noformat}
> The first rule means that if the user queue doesn't exist, it should be
> created as {{root.}}.
> The second means the same thing, except refers to the primary group instead
> of the submitting user: {{root.}}.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10620) fs2cs: parentQueue for certain placement rules are not set during conversion
[
https://issues.apache.org/jira/browse/YARN-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko updated YARN-10620:
Attachment: YARN-10620-001.patch
> 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
> Attachments: YARN-10620-001.patch
>
>
> There are some placement rules in FS which are currently not handled properly
> by fs2cs:
> {noformat}
>
>
>
>
> {noformat}
> The first rule means that if the user queue doesn't exist, it should be
> created as {{root.}}.
> The second means the same thing, except refers to the primary group instead
> of the submitting user: {{root.}}.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10620) fs2cs: parentQueue for certain placement rules are not set during conversion
[
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}
{noformat}
The first rule means that if the user queue doesn't exist, it should be created
as {{root.}}.
The second means the same thing, except refers to the primary group instead of
the submitting user: {{root.}}.
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}
>
>
>
>
> {noformat}
> The first rule means that if the user queue doesn't exist, it should be
> created as {{root.}}.
> The second means the same thing, except refers to the primary group instead
> of the submitting user: {{root.}}.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
