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 2016/07/20 21:37:20 UTC

[jira] [Comment Edited] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

    [ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386676#comment-15386676 ] 

Arun Suresh edited comment on YARN-5392 at 7/20/16 9:36 PM:
------------------------------------------------------------

[~leftnoteasy], I understand we've touched a lot of the code, but our thinking was that:
# replacing Priority with SchedulerKey means we actually do NOT have to change core logic. As you can see, It is almost always a strict replacement of Priority with SchedulerKey, there is very little logic change in this patch if you see.
# also, like I mentioned earlier, having something like SchedulerKey means we won't have to change any more code later, if say we decide we need some other parameter to prioritize scheduling decisions. We can even choose to ignore current attributes like priority for a deployment if we want, based on configuration (if we make the SchedulerKey truly pluggable.. but that can be another JIRA)


was (Author: asuresh):
[~leftnoteasy], I understand we've touched a lot of the code, but our thinking was that:
# replacing Priority with SchedulerKey means we actually do NOT have to change core logic. As you can see, It is almost always a strict replacement of Priority with SchedulerKey.
# also, like I mentioned earlier, having something like SchedulerKey means we won't have to change any more code later, if say we decide we need some other parameter to prioritize scheduling decisions. We can even choose to ignore current attributes like priority for a deployment if we want, based on configuration (if we make the SchedulerKey truly pluggable.. but that can be another JIRA)

> Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-5392
>                 URL: https://issues.apache.org/jira/browse/YARN-5392
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>         Attachments: YARN-5392.001.patch, YARN-5392.002.patch, YARN-5392.003.patch, YARN-5392.004.patch
>
>
> Based on discussions in YARN-4888, this jira proposes to replace the use of {{Priority}} in the Scheduler infrastructure (Scheduler, Queues, SchedulerApp / Node etc.) with a more opaque and extensible {{SchedulerKey}}.
> Note: Even though {{SchedulerKey}} will be used by the internal scheduling infrastructure, It will not be exposed to the Client or the AM. The SchdulerKey is meant to be an internal construct that is derived from attributes of the ResourceRequest / ApplicationSubmissionContext / Scheduler Configuration etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org