[
https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303099#comment-15303099
]
Arun Suresh commented on YARN-5124:
-----------------------------------
[~kkaranasos], Thanks for the review..
I was actually in quite a dilemma about where to place the ExecutionType. Then
I looked at the {{AppSchedulingInfo}} class which is used by the RM to maintain
the outstanding Requests.
The key used there is just : Priority -> String(ResourceName) .. Which
implies that the Resource(capability) is not really a key. Please take a look
at the discussion on YARN-314 for more context.
Which leads me to think we should remove Resource from the key entirely in the
AMRMClient.. but since the scope of this JIRA was to add ExecutionType in the
key, I decided to put it before the Resource, in case the Resource gets dropped
later on.. Hope this makes sense..
> Modify AMRMClient to set the ExecutionType in the ResourceRequest
> -----------------------------------------------------------------
>
> Key: YARN-5124
> URL: https://issues.apache.org/jira/browse/YARN-5124
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: YARN-5124.001.patch, YARN-5124.002.patch,
> YARN-5124.003.patch, YARN-5124.004.patch, YARN-5124.005.patch,
> YARN-5124.006.patch
>
>
> Currently the {{ContainerRequest}} allows the AM to set the {{ExecutionType}}
> in the AMRMClient, but it is not being set in the actual {{ResourceRequest}}
> that is sent to the RM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
