[
https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297287#comment-15297287
]
Wangda Tan commented on YARN-5087:
----------------------------------
Hi [~asuresh],
I think there's a downside of merging all property-changes of a container into
a single protocol.
If changes cannot be done within the same heartbeat, and there're a couple of
changes required for a given container (like execution type / resource, etc.),
when we should response back to AM is a problem: should we immediately report
back to AM when any of the change requests is done OR should we wait for all
change requests are done?
And if we merge different kinds of changes to the original allocatedContainers
/ updatedContainers, application could be hard to figure out what changes are
applied. Yes application can remember their containers original properties, but
IMO it is not as simple as clearly tell you what changes have done containers.
That is also way we chose to separate updateResource to increase/decrease
resource protocol:
Please let me know your thoughts.
> 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]
