[
https://issues.apache.org/jira/browse/YARN-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960755#comment-15960755
]
Jason Lowe commented on YARN-6443:
----------------------------------
Ah, so this apparently is describing a problem that only can occur if scheduler
keys are being used? I'm not sure we need a flag here. Seems like we simply
should not guarantee that allocations are returned within a priority group in
the order they are requested -- they can be returned in any order. It
certainly worked that way without scheduler keys. If you need ordering, that's
what priorities are for. In that sense I see this not as an enhancement but
rather a bugfix. Or am I misunderstanding the problem?
> Allow for Priority order relaxing in favor of improved node/rack locality
> --------------------------------------------------------------------------
>
> Key: YARN-6443
> URL: https://issues.apache.org/jira/browse/YARN-6443
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler, fairscheduler
> Reporter: Arun Suresh
> Assignee: Hitesh Sharma
>
> Currently the Schedulers examine an applications pending Requests in Priority
> order. This JIRA proposes to introduce a flag (either via the
> ApplicationMasterService::registerApplication() or via some Scheduler
> configuration) to favor an ordering that is baised to the node that is
> currently heartbeating by relaxing the priority constraint.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
