[
https://issues.apache.org/jira/browse/YARN-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068874#comment-16068874
]
Konstantinos Karanasos commented on YARN-6594:
----------------------------------------------
Hi [~jianhe], glad to hear you will be using the new API.
Re: your question on nesting the ResourceSizing object, I did it this way to
align with what we discussed offline with
[~asuresh]/[~curino]/[~chris.douglas]/[~subru]/[~vinodkv]/[~leftnoteasy].
Essentially, it is cleaner to separate the sizing object. Also we might need to
add more fields to it later, which will end up making the SchedulingRequest
object too bulky.
To make it easier for the applications, like you point out, I will make sure in
the next version I add a constructor in the SchedulingRequest that
automatically creates the ResourceSizing objects, given a number of allocations
and resources.
Hope it makes sense.
> [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]
