[
https://issues.apache.org/jira/browse/YARN-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandni Singh updated YARN-8160:
--------------------------------
Description:
Ability to upgrade dockerized yarn native services.
Ref: YARN-5637
*Background*
Container upgrade is supported by the NM via {{reInitializeContainer}} api.
{{reInitializeContainer}} does *NOT* change the ContainerId of the upgraded
container.
NM performs the following steps during {{reInitializeContainer}}:
- kills the existing process
- cleans up the container
- launches another container with the new {{ContainerLaunchContext}}
NOTE: {{ContainerLaunchContext}} holds all the information that needs to
upgrade the container.
With {{reInitializeContainer}}, the following does *NOT* change
- container ID. This is not created by NM. It is provided to it and here RM is
not creating another container allocation.
- {{localizedResources}} this stays the same if the upgrade does *NOT* require
additional resources IIUC.
The following changes with {{reInitializeContainer}}
- the working directory of the upgraded container changes. It is *NOT* a
relaunch.
was:
Ability to upgrade dockerized yarn native services.
Ref: YARN-5637
Container upgrade is supported by the NM via {{reInitializeContainer}} api.
{{reInitializeContainer}} does *NOT* change the ContainerId of the upgraded
container.
{{reInitializeContainer}} of the container on the NM performs these steps:
- kill the existing process
- cleanup the container
- launch another container with the new {{ContainerLaunchContext}}
With {{reInitializeContainer}}, the following does *NOT* change
- container ID. This is not created by NM. It is provided to it and here RM is
not creating another container allocation.
- {{localizedResourcess}} this stays the same if the upgrade does *NOT* require
additional resources IIUC.
The following changes with {{reInitializeContainer}}
- the working directory of the upgraded container changes.
> Yarn Service Upgrade: Support upgrade of service that use docker containers
> ----------------------------------------------------------------------------
>
> Key: YARN-8160
> URL: https://issues.apache.org/jira/browse/YARN-8160
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Chandni Singh
> Assignee: Chandni Singh
> Priority: Major
> Labels: Docker
>
> Ability to upgrade dockerized yarn native services.
> Ref: YARN-5637
> *Background*
> Container upgrade is supported by the NM via {{reInitializeContainer}} api.
> {{reInitializeContainer}} does *NOT* change the ContainerId of the upgraded
> container.
> NM performs the following steps during {{reInitializeContainer}}:
> - kills the existing process
> - cleans up the container
> - launches another container with the new {{ContainerLaunchContext}}
> NOTE: {{ContainerLaunchContext}} holds all the information that needs to
> upgrade the container.
> With {{reInitializeContainer}}, the following does *NOT* change
> - container ID. This is not created by NM. It is provided to it and here RM
> is not creating another container allocation.
> - {{localizedResources}} this stays the same if the upgrade does *NOT*
> require additional resources IIUC.
>
> The following changes with {{reInitializeContainer}}
> - the working directory of the upgraded container changes. It is *NOT* a
> relaunch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
