[
https://issues.apache.org/jira/browse/YARN-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216107#comment-15216107
]
Karthik Kambatla commented on YARN-4879:
----------------------------------------
Thanks for putting the doc together with all the details. Would be nice to
capture details on when we would delete the ResourceRequests altogether from
AppSchedulingInfo.
While making these changes, would it possible to address YARN-314 too?
> Proposal for a simple (delta) allocate protocol
> -----------------------------------------------
>
> Key: YARN-4879
> URL: https://issues.apache.org/jira/browse/YARN-4879
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: applications, resourcemanager
> Reporter: Subru Krishnan
> Assignee: Subru Krishnan
> Attachments: SimpleAllocateProtocolProposal-v1.pdf
>
>
> For legacy reasons, the current allocate protocol expects expanded requests
> which represent the cumulative request for any change in resource
> constraints. This is not only very difficult to comprehend but makes it
> impossible for the scheduler to associate container allocations to the
> original requests. This problem is amplified by the fact that the expansion
> is managed by the AMRMClient which makes it cumbersome for non-Java clients
> as they all have to replicate the non-trivial logic. In this JIRA, we are
> proposing a delta allocate protocol where the AM will need to only specify
> changes in resource constraints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
