[
https://issues.apache.org/jira/browse/YARN-10043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000157#comment-17000157
]
Manikandan R commented on YARN-10043:
-------------------------------------
Thanks [~wilfreds].
FairOrderingPolicy (FO) does the following:
Compare resource usage of 2 schedulables and give preferences to one with
lesser usages. Only If {{fair.enable-size-based-weight}} has been enabled, then
preference would be given to the one with more demand, with the intent to
favour large apps when many smaller ones enter and leave the queue continuously.
FairSharePolicy of FS does the following:
# Compare demands. Schedulable without resource demand get lower priority than
ones who have demands.
# Compare MinShareUsage
# Compare FairShareUsage
# Compare using job submit time
# Compare using job name
Except #3, other comparisons are missing in FO. #3 is bit closer to
{{{{fair.enable-size-based-weight}}}} based flow in FO, but has some
differences. For example, app priority has been taken into consideration in
FairSharePolicy during weight calculation.
Proposal is to add these missed comparisons steps in the same order. But I am
bit skeptical about adding #2, not really sure whether it is possible and makes
sense.
Thoughts?
> FairOrderingPolicy Improvements
> -------------------------------
>
> Key: YARN-10043
> URL: https://issues.apache.org/jira/browse/YARN-10043
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
>
> FairOrderingPolicy can be improved by using some of the approaches (only
> relevant) implemented in FairSharePolicy of FS. This improvement has
> significance in FS to CS migration context.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
