hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey
Date Thu, 21 Jul 2016 14:30:21 GMT

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

Arun Suresh commented on YARN-5392:

[~sunilg], true... also it seems to be used only in testclasses. Did not want to increase
this patch size more than already required..
Feel free to file another JIRA that depends on / blocked by this one

> 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,
YARN-5392.005.patch, YARN-5392.006.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

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

View raw message