[
https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated YARN-5392:
------------------------------
Description:
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 /
was: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}}.
> 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
>
>
> 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 /
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
