[
https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297367#comment-15297367
]
Wangda Tan commented on YARN-5087:
----------------------------------
[~asuresh],
bq. 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.
It could be problematic as well, for example, how RM response back if later
requested change can be earlier updated? (application request increase
container first, then request update container priority, assume container
priority can be updated in no time).
So I would suggest to separate container properties updating to different
fields of AllocateRequest.
bq. 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 ?
We don't allow request increase/decrease for same container-id on one
heartbeat. If they come in different heartbeats, later requested change will
overwrite previous requested change.
> 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]
