[
https://issues.apache.org/jira/browse/YARN-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045791#comment-17045791
]
Brahma Reddy Battula commented on YARN-8286:
[~billie] and [~adam.antal], could we move to 3.4 if this is not critical for
3.3.? will cut branch-3.3 by next week.
* [|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13161175]
> Inform AM of container relaunch
> ---
>
> Key: YARN-8286
> URL: https://issues.apache.org/jira/browse/YARN-8286
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Billie Rinaldi
>Assignee: Adam Antal
>Priority: Critical
>
> The AM may need to perform actions when a container has been relaunched. For
> example, the service AM would want to change the state it has recorded for
> the container and retrieve new container status for the container, in case
> the container IP has changed. (The NM would also need to remove the IP it has
> stored for the container, so container status calls don't return an IP for a
> container that is not currently running.)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
