[
https://issues.apache.org/jira/browse/YARN-9892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016112#comment-17016112
]
Wangda Tan commented on YARN-9892:
----------------------------------
[~pbacsko], [~maniraj...@gmail.com] , thanks for working on this.
Sorry for chiming in late, I have several questions:
1) What is the use case of allowing app's DRF sort only? (While other
computations are using memory only). I saw it is under FS -> CS conversion
tool, but is it a feature we really want to support?
2) In CS, IIRC when DRF is disabled, all the resource accounting will only look
at memory. For example, a queue which set 100 vcore max limit will not be
respected, asking 100 vcore is the same as asking 0 vore. In that case, I don't
think look at DRF of apps is meaningful.
cc: [~sunilg] , [~wilfreds] to add some thoughts here.
> Capacity scheduler: support DRF ordering policy on queue level
> --------------------------------------------------------------
>
> Key: YARN-9892
> URL: https://issues.apache.org/jira/browse/YARN-9892
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler
> Reporter: Peter Bacsko
> Assignee: Manikandan R
> Priority: Major
> Attachments: YARN-9892-003.patch, YARN-9892.001.patch,
> YARN-9892.002.patch
>
>
> Capacity scheduler does not support DRF (Dominant Resource Fairness) ordering
> policy on queue level. Only "fifo" and "fair" are accepted for
> {{yarn.scheduler.capacity.<queue-path>.ordering-policy}}.
> DRF can only be used globally if
> {{yarn.scheduler.capacity.resource-calculator}} is set to
> DominantResourceCalculator.
--
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
