You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Arun Suresh (JIRA)" <ji...@apache.org> on 2017/04/05 05:09:42 UTC
[jira] [Commented] (YARN-6443) Allow for Priority order relaxing in
favor of improved node/rack locality
[ https://issues.apache.org/jira/browse/YARN-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956309#comment-15956309 ]
Arun Suresh commented on YARN-6443:
-----------------------------------
My initial though was: instead of simply iterating over appschedingInfo::getSchedulerKeys(), we have a Policy that takes the current Node and returns an iterator with SchedulerKeys that have ResourceRequests with the current node as ResourceName bubble to the top.
[~jlowe], [~leftnoteasy], [~kasha], [~vinodkv], [~curino], [~kkaranasos] Thoughts ?
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org