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 "Sunil Govindan (JIRA)" <ji...@apache.org> on 2018/11/17 03:23:06 UTC
[jira] [Updated] (YARN-5674) FairScheduler handles "dots" in user
names inconsistently in the config
[ https://issues.apache.org/jira/browse/YARN-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunil Govindan updated YARN-5674:
---------------------------------
Target Version/s: 3.3.0 (was: 3.2.0)
Bulk update: moved all 3.2.0 non-blocker issues, please move back if it is a blocker.
> FairScheduler handles "dots" in user names inconsistently in the config
> -----------------------------------------------------------------------
>
> Key: YARN-5674
> URL: https://issues.apache.org/jira/browse/YARN-5674
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Affects Versions: 2.6.0
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
> Priority: Major
>
> A user name can contain a dot because it could be used as the queue name we replace the dot with a defined separator. When defining queues in the configuration for users containing a dot we expect that the dot is replaced by the "\_dot\_" string.
> In the user limits we do not do that and user limits need a normal dot in the user name. This is confusing when you create a scheduler configuration in some places you need to replace in others you do not. This can cause issue when user limits are not enforced as expected.
> We should use one way to specify the user and since the queue naming can not be changed we should also use the same "\_dot\_" in the user limits and enforce correctly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org