[
https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated YARN-5221:
------------------------------
Attachment: YARN-5221.009.patch
Thanks for the thoughtful review [~subru]. Updating the patch to rebase with
trunk and kick of jenkins.
I have also updated it your suggestions, as part of which I have introduced an
enum {{ContainerUpdateType}} used both in the {{AllocateRequest}} to limit the
update to either a Container capability increase / decrease or ExecutionType.
bq. .. can we defer splitting increase/decreaseRequests to the actual
Scheduler..
I totally agree. I wanted this patch to be more about refactoring / fixing the
user facing aspects of YARN-1651. I will raise another JIRA to refactor some of
these internals.
> Expose UpdateResourceRequest API to allow AM to request for change in
> container properties
> ------------------------------------------------------------------------------------------
>
> Key: YARN-5221
> URL: https://issues.apache.org/jira/browse/YARN-5221
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: YARN-5221.001.patch, YARN-5221.002.patch,
> YARN-5221.003.patch, YARN-5221.004.patch, YARN-5221.005.patch,
> YARN-5221.006.patch, YARN-5221.007.patch, YARN-5221.008.patch,
> YARN-5221.009.patch
>
>
> YARN-1197 introduced APIs to allow an AM to request for Increase and Decrease
> of Container Resources after initial allocation.
> YARN-5085 proposes to allow an AM to request for a change of Container
> ExecutionType.
> This JIRA proposes to unify both of the above into an Update Container API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
