[
https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385055#comment-15385055
]
Subru Krishnan commented on YARN-5392:
--------------------------------------
Thanks [~asuresh] for working on this.
I just have one question, should we have the {{SchedulerKey}} in addition to
{{Priority}}?
I feel {{Priority}} should be accessible directly as before outside of the
scheduler layers and the notion of {{SchedulerKey}} should be confined to the
scheduler (ideally should be transparent to other RM entities/services). An
extreme example would be that in future we could decide not to use {{Priority}}
as a {{SchedulerKey}} at some point in the future.
Overall the patch LGTM. Since I have been working very closely with you;
[~kasha]/[~leftnoteasy], can you guys take a look.
> 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 / ApplicationSubmissionContext / Scheduler
> Configuration etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
