Peter Bacsko created YARN-10099:
-----------------------------------
Summary: FS-CS converter: handle allow-undeclared-pools and
user-as-default queue properly
Key: YARN-10099
URL: https://issues.apache.org/jira/browse/YARN-10099
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Peter Bacsko
Assignee: Peter Bacsko
Based on the latest documentation, there are two important properties that are
ignored if we have placement rules:
||Property||Explanation||
|yarn.scheduler.fair.allow-undeclared-pools|If this is true, new queues can be
created at application submission time, whether because they are specified as
the application’s queue by the submitter or because they are placed there by
the user-as-default-queue property. If this is false, any time an app would be
placed in a queue that is not specified in the allocations file, it is placed
in the “default” queue instead. Defaults to true. *If a queue placement policy
is given in the allocations file, this property is ignored.*|
|yarn.scheduler.fair.user-as-default-queue|Whether to use the username
associated with the allocation as the default queue name, in the event that a
queue name is not specified. If this is set to “false” or unset, all jobs have
a shared default queue, named “default”. Defaults to true. *If a queue
placement policy is given in the allocations file, this property is ignored.*|
| | |
Right now these settings affects the conversion regardless of the placement
rules.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
