[
https://issues.apache.org/jira/browse/YARN-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956947#comment-15956947
]
Jason Lowe commented on YARN-6443:
----------------------------------
Could you elaborate a bit on the use case where an application bothers to
specify different priorities for requests but is OK with having a lower
priority request be allocated first because locality was better? Now that
there are scheduler keys to help match allocations back to their original
requests, it seems priority really can be a priority rather than a hack to help
match them. If the app doesn't really care what order two different kinds of
requests are given in as long as they have good locality, why not just submit
them at the same priority instead of having this extra flag?
> 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: Arun Suresh
>
> 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
