[
https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297314#comment-15297314
]
Arun Suresh commented on YARN-5087:
-----------------------------------
Thanks for weighing in [~leftnoteasy],
If we restrict an update to be only one type of change (for eg. if you want to
change BOTH execution type and increase resources, you would need to add 2
UpdateContainerRequest entries against the same container), then the RM can
process them in order and return the responses in order.
But I agree, it might be disruptive for 2.8.. can we target 2.9 or 3.0 then ?
By the way, I was just thinking... in the current scheme (having a separate
increase ContainerResourceRequest list and decrease ContainerResourceRequest
list), what happens when a user asks for both increase and decrease resource
for the same Container Id, Is there an order in which it is processed currently
at the RM ?
> Expose API to allow AM to request for change of container ExecutionType
> -----------------------------------------------------------------------
>
> Key: YARN-5087
> URL: https://issues.apache.org/jira/browse/YARN-5087
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
