[
https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261552#comment-16261552
]
Jian He commented on YARN-6168:
-------------------------------
A minor optimization for pullPreviousAttemptContainers : we could add a check
if the size == 0, return.
could you add a little comment:
for pullContainersToTransfer, // called when AM registers
for pullPreviousAttemptContainers, // called when AM heartbeats if there are
containers not reported in register.
> 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
> Assignee: Chandni Singh
> Attachments: YARN-6168.001.patch, YARN-6168.002.patch,
> YARN-6168.003.patch
>
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
