[
https://issues.apache.org/jira/browse/YARN-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446061#comment-16446061
]
Eric Yang commented on YARN-7939:
---------------------------------
[~csingh] This is not a docker app. There is nothing related to docker in the
example that I launched. I am not sure relaunch logic only applies to docker
app, it seems to be triggered without docker. Container-executor is trying to
run launch_container.sh, but an existing copy is already existed. This cause
container-executor to fail, and report back as failure, then another instance
is spawned on another node. The container was not initialized on the new node.
This caused the container to show as running, but there is nothing running on
the new node. I am going to try to revert YARN-7973 locally and see if the
same behavior occurs.
> Yarn Service Upgrade: add support to upgrade a component instance
> ------------------------------------------------------------------
>
> Key: YARN-7939
> URL: https://issues.apache.org/jira/browse/YARN-7939
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Chandni Singh
> Assignee: Chandni Singh
> Priority: Major
> Attachments: YARN-7939.001.patch, YARN-7939.002.patch,
> YARN-7939.003.patch, YARN-7939.004.patch, YARN-7939.005.patch,
> YARN-7939.006.patch, YARN-7939.007.patch, YARN-7939.008.patch
>
>
> Yarn core supports in-place upgrade of containers. A yarn service can
> leverage that to provide in-place upgrade of component instances. Please see
> YARN-7512 for details.
> Will add support to upgrade a single component instance first and then
> iteratively add other APIs and features.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
