hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers
Date Mon, 20 Nov 2017 22:30:00 GMT

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

Jian He commented on YARN-6168:

could you also add more detailed comments in AllocateResponse#get/setContainersFromPreviousAttempts
to explain the scenario the containers might not be received in the previous register call

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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message