[
https://issues.apache.org/jira/browse/YARN-9751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911903#comment-16911903
]
Jonathan Hung commented on YARN-9751:
-------------------------------------
Thanks [~leftnoteasy] -
{quote} - If admin configures ordering-policy only, it should apply to both
queue and app.{quote}
Behavior from this patch is: configured ordering policy will only apply to
queue. For app, it will just use DEFAULT_APP_ORDERING_POLICY. I think it makes
sense not to conflate the two (ordering-policy <-> queue, and
app-ordering-policy <-> app, each config has no relation to the other).
{quote} - If admin configures ordering-policy and app-ordering-policy, queue
and app policies could be different.{quote}
Yes that's correct.
> Separate queue and app ordering policy capacity scheduler configs
> -----------------------------------------------------------------
>
> Key: YARN-9751
> URL: https://issues.apache.org/jira/browse/YARN-9751
> Project: Hadoop YARN
> Issue Type: Task
> Reporter: Jonathan Hung
> Assignee: Jonathan Hung
> Priority: Major
> Labels: release-blocker
> Attachments: YARN-9751.001.patch
>
>
> Right now it's not possible to specify distinct app and queue ordering
> policies since they share the same {{ordering-policy}} suffix.
> There's already a TODO in CapacitySchedulerConfiguration for this. This Jira
> intends to fix it.
> {noformat}
> // TODO (wangda): We need to better distinguish app ordering policy and queue
> // ordering policy's classname / configuration options, etc. And dedup code
> // if possible.{noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
