You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Chandni Singh (JIRA)" <ji...@apache.org> on 2018/08/01 18:16:00 UTC
[jira] [Updated] (YARN-8160) Yarn Service Upgrade: Support upgrade
of service that use docker containers
[ 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
Ref: YARN-5637
Ability to upgrade dockerized yarn native services.
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}}
The Container Id does NOT change because NM doesn't create the ContainerId. It is provided to it by the AM and here the RM is not involved in creating a new container allocation.
was:
Ability to upgrade dockerized yarn native services.
Ref: YARN-5637
> 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
> Ref: YARN-5637
> Ability to upgrade dockerized yarn native services.
> 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}}
> The Container Id does NOT change because NM doesn't create the ContainerId. It is provided to it by the AM and here the RM is not involved in creating a new container allocation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org