[
https://issues.apache.org/jira/browse/YARN-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214708#comment-15214708
]
Subru Krishnan commented on YARN-4879:
--------------------------------------
bq. Everything looks good and easy to read and understand.
Thanks [~giovanni.fumarola] for looking at our proposal and providing feedback.
bq. Are you going to add the ResourceRequestId as field of Container?
Yes. That is how AMs can map the allocated container to their actual request.
bq. You will not need a int field in the map, because it is already part of the
ResourceRequest. Do you want to keep the map ordered by ID?
Good catch. This is the exact question that [~asuresh] raised. A list is
sufficient but I am leaning towards Map for making the accounting process more
simple/fast.
For e.g.: If a node local allocation is made for node N1, we can immediately
lookup the entries for rack and ANY by using the ID key and decrement them
instead of linearly scanning the rack/ANY entries.
Yes, we want to use a sorted map. The reason for doing that is we want to start
with a FIFO allocation order.
> 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)
