[
https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297089#comment-15297089
]
Carlo Curino commented on YARN-5124:
------------------------------------
Based on our off-line conversation, the current patch would prevent us to have
ResourceRequests of different container types at the same priority level. This
is in principle bad, as it forces users to use different priority levels, that
then would be ignored by the implementation (as the decisions for guaranteed /
opportunistic are done in different places).
I think the cleaner semantic should be:
# I can ask for different container types at the same priority level
# Priority ranks for different container types are non-comparable (i.e., G@P0
might be served before or after O@P1).
This could/should probably be implemented leveraging the work going on in
YARN-4887?
[~kkaranasos],[~subru] and [~asuresh] thoughts?
> 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
>
>
> 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]
