You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Bibin A Chundatt (JIRA)" <ji...@apache.org> on 2018/11/12 08:50:00 UTC

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

     [ https://issues.apache.org/jira/browse/YARN-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bibin A Chundatt updated YARN-8980:
-----------------------------------
    Description: 
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.

issue credits : [~Nallasivan]
 

  was:
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.


 


> 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.
> issue credits : [~Nallasivan]
>  



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