[
https://issues.apache.org/jira/browse/YARN-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441660#comment-16441660
]
Eric Yang commented on YARN-8160:
---------------------------------
[~csingh] When I trigger upgrade to happen on docker container for YARN-7939
testing, the existing container shutdown correctly, but relaunch did not bring
up any docker container. Shane's concern over docker start retaining all
existing parameters is a real problem. This could prevent upgrade from using
relaunch to start the container because some parameters might need to be
changed. On the other hand, we may have problems that if end user application
encode hostname or IP address to their application. Launching new containers
might break existing user application. It is hard to say, which approach is
safer, but I am leaning toward launch new containers while try to preserve
hostname / IP as much as possible. This means we need similar code path as
relaunch, but not depend on "docker start", and pass in new docker run commad.
[[email protected]] is this something that can be done by refactoring
relaunch code to accommodate for upgrade use case?
> 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
>
> Ability to upgrade dockerized yarn native services.
> Ref: YARN-5637
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
