[
https://issues.apache.org/jira/browse/YARN-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103986#comment-16103986
]
Arun Suresh edited comment on YARN-6594 at 7/27/17 10:01 PM:
-------------------------------------------------------------
Given that YARN-6593 looks close to committing, Think we should move forward
with this.
[~leftnoteasy] / [~jianhe], we should discuss further about the changes to the
AMRMClient in YARN-6619
was (Author: asuresh):
Given that YARN-6593 looks close to committing, Think we should move forward
with this.
[~leftnoteasy] / [~jianhe], this we should discuss further about the changes to
the AMRMClient in YARN-6619
> [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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]