[ https://issues.apache.org/jira/browse/YARN-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15518350#comment-15518350
]
Jian He commented on YARN-5609:
-------------------------------
I see, I'm ok to not use the same method. The main thing I'm referring is that the containersReIniting
counter may not be decremented if the container failed to reInit or succeed on reInit ? It
only decrements when the container successfully reInited. This will cause the containersReIniting
stay at a positive value forever, right ?
> 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-5609.003.patch, YARN-5609.004.patch,
YARN-5609.005.patch, YARN-5609.006.patch, YARN-5609.007.patch, YARN-5609.008.patch, YARN-5609.009.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:
> * *reInitializeContainer*
> * *rollbackLastUpgrade*
> * *commitLastUpgrade*
> * *restartContainer*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org