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 "Wangda Tan (JIRA)" <ji...@apache.org> on 2017/05/18 01:08:04 UTC
[jira] [Commented] (YARN-6594) [API] Introduce SchedulingRequest
object
[ https://issues.apache.org/jira/browse/YARN-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015021#comment-16015021 ]
Wangda Tan commented on YARN-6594:
----------------------------------
Thanks [~kkaranasos], from a rough look, generally looks good to me.
Few comments:
1) There's a {{@Stable}} method, is it better to change to unstable since all others are unstable?
2) ExecutionType is added to SchedulingRequest, I just not sure if it is a best place to add. Let's keep it now and revisit it in the future.
> [API] Introduce SchedulingRequest object
> ----------------------------------------
>
> Key: YARN-6594
> URL: https://issues.apache.org/jira/browse/YARN-6594
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Konstantinos Karanasos
> Assignee: Konstantinos Karanasos
> Attachments: YARN-6594.001.patch
>
>
> This JIRA introduces a new SchedulingRequest object.
> It will be part of the {{AllocateRequest}} and will be used to define sizing (e.g., number of allocations, size of allocations) and placement constraints for allocations.
> Applications can use either this new object (when rich placement constraints are required) or the existing {{ResourceRequest}} object.
--
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