[jira] [Comment Edited] (YARN-8980) Mapreduce application container start fail after AM restart.

["Bibin A Chundatt (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YARN-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682255#comment-16682255 ] 

Bibin A Chundatt edited comment on YARN-8980 at 11/10/18 7:23 AM:
------------------------------------------------------------------

cc : [~botong]

Incase o fMapreduce application for initial containers after AM restart, containers are assigned without NMToken, ContainerLaunches are failing with invalid token for containers assigned from secondary subclusters.



was (Author: bibinchundatt):
cc : [~botong]

Mapreduce application for initial containers after restart containers are assigned without NMToken, ContainerLaunches are failing with invalid token for containers assigned from secondary subclusters.


> Mapreduce application container start  fail after AM restart.
> -------------------------------------------------------------
>
>                 Key: YARN-8980
>                 URL: https://issues.apache.org/jira/browse/YARN-8980
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Bibin A Chundatt
>            Priority: Major
>
> UAM to subclusters are always launched with keepContainers.
> On AM restart scenarios , UAM register again with RM . UAM receive running containers with NMToken. NMToken received by UAM in getPreviousAttemptContainersNMToken is never used by mapreduce application.  
> Federation Interceptor should take care of such scenarios too. Merge NMToken received at registration to allocate response.
> Container allocation response on same node will have NMToken empty.
>  



--
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