[
https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947305#comment-15947305
]
Billie Rinaldi commented on YARN-6168:
--------------------------------------
Yes. In my case, the AM requested new containers immediately and got them
allocated, so when it was informed later about the old containers, it just
released them.
> Restarted RM may not inform AM about all existing containers
> ------------------------------------------------------------
>
> Key: YARN-6168
> URL: https://issues.apache.org/jira/browse/YARN-6168
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Billie Rinaldi
>
> There appears to be a race condition when an RM is restarted. I had a
> situation where the RMs and AM were down, but NMs and app containers were
> still running. When I restarted the RM, the AM restarted, registered with the
> RM, and received its list of existing containers before the NMs had reported
> all of their containers to the RM. The AM was only told about some of the
> app's existing containers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
