[
https://issues.apache.org/jira/browse/YARN-10254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17102597#comment-17102597
]
Peter Bacsko edited comment on YARN-10254 at 5/8/20, 1:38 PM:
--------------------------------------------------------------
Regarding #2 I'm voting for throwing an exception.
For example, I use the mapping "u:%user:root.grp.%primary_group", but the
administrator changes the queue structure to "root.groups" from "root.grp". The
mapping becomes invalid and all (or some) applications end up running in
"root.default". In situatons like that, I prefer seeing a failure immediately
so I can act ASAP. Having a running app might be preferable in some scenarios,
but it will likely affect the SLAs and job running times. The users have to
realize that their application have been placed into the wrong queue and it
takes time. These kind of problems can be enormously frustrating.
was (Author: pbacsko):
Regarding #2 I would vot for throwing an exception.
For example, I use the mapping "u:%user:root.grp.%primary_group", but the
administrator changes the queue structure to "root.groups" from "root.grp". The
mapping becomes invalid and all (or some) applications end up running in
"root.default". In situatons like that, I prefer seeing a failure immediately
so I can act ASAP. Having a running app might be preferable in some scenarios,
but it will likely affect the SLAs and job running times. The users have to
realize that their application have been placed into the wrong queue and it
takes time. These kind of problems can be enormously frustrating.
> CapacityScheduler incorrect User Group Mapping after leaf queue change
> ----------------------------------------------------------------------
>
> Key: YARN-10254
> URL: https://issues.apache.org/jira/browse/YARN-10254
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Gergely Pollak
> Assignee: Gergely Pollak
> Priority: Major
> Attachments: YARN-10254.001.patch, YARN-10254.002.patch
>
>
> YARN-9879 and YARN-10198 introduced some major changes to user group mapping,
> and some of them unfortunately had some negative impact on the way mapping
> works.
> In some cases incorrect PlacementContexts were created, where full queue path
> was passed as leaf queue name. This affects how the yarn cli app list
> displays the queues.
> u:%user:%primary_group.%user mapping fails with an incorrect validation error
> when the %primary_group parent queue was a managed parent.
> Group based rules in certain cases are mapped to root.[primary_group] rules,
> loosing the ability to create deeper structures.
>
--
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
