[
https://issues.apache.org/jira/browse/YARN-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated YARN-5609:
------------------------------
Attachment: YARN-5609.002.patch
Uploading patch based on [~jianhe]'s suggestions. Thanks of the review !!
* Also fixing testcase errors (which was due to the fact that the launch
context was null.. good catch Jian)
* Added some basic authorization check to see if the remoteUgi and
NMTokenIdentifier presented by the caller is correct. Wondering if we need to
also ensure that only the application that started the container can
reinitialize it. Do we need this for the localize api as well ? Thoughts
[~jianhe] ?
> Expose upgrade and restart API in ContainerManagementProtocol
> -------------------------------------------------------------
>
> Key: YARN-5609
> URL: https://issues.apache.org/jira/browse/YARN-5609
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: YARN-5609.001.patch, YARN-5609.002.patch
>
>
> YARN-5620 and YARN-5637 allows an AM to explicitly *upgrade* a container with
> a new launch context and subsequently *rollback* / *commit* the change on the
> Container. This can also be used to simply *restart* the Container as well.
> This JIRA proposes to extend the ContainerManagementProtocol with the
> following API:
> * *upgradeContainer*
> * *rollbackLastUpgrade*
> * *commitLastUpgrade*
> * *restartContainer*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
