[
https://issues.apache.org/jira/browse/YARN-8265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471183#comment-16471183
]
Billie Rinaldi commented on YARN-8265:
--------------------------------------
It seems like we have a few options (in order from most to least desirable):
# implement a new callback so that the NM can inform the AM of container
relaunch and have the AM handle the relaunch
# if we can't do the NM callback right now, we could work around the issue by
having the AM continue to retrieve container status for docker containers
forever (perhaps only for docker containers that are not using the host
network), so the AM can find out if the container IP changes. This would result
in a lot of unnecessary status calls, but seems like it would be a feasible
workaround
# disable container retry for docker containers for now
# do nothing for now, and this will be a known bug
Any thoughts, [~leftnoteasy] [~vinodkv]?
> AM should retrieve new IP for restarted container
> -------------------------------------------------
>
> Key: YARN-8265
> URL: https://issues.apache.org/jira/browse/YARN-8265
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-native-services
> Affects Versions: 3.1.0
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Critical
> Fix For: 3.2.0, 3.1.1
>
> Attachments: YARN-8265.001.patch
>
>
> When a docker container is restarted, it gets a new IP, but the service AM
> only retrieves one IP for a container and then cancels the container status
> retriever. I suspect the issue would be solved by restarting the retriever
> (if it has been canceled) when the onContainerRestart callback is received,
> but we'll have to do some testing to make sure this works.
--
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
