[
https://issues.apache.org/jira/browse/YARN-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subru Krishnan updated YARN-4879:
---------------------------------
Description: 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 enhancement to the Allocate Protocol to allow AMs to identify
requests explicitly. (was: 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. )
> Enhance Allocate Protocol to Identify Requests Explicitly
> ---------------------------------------------------------
>
> 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 enhancement to the Allocate Protocol to allow AMs to identify
> requests explicitly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
