hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chandni Singh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers
Date Thu, 09 Nov 2017 23:10:00 GMT

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

Chandni Singh commented on YARN-6168:

The default value of {{nmExpiryInterval}} is 10 minutes. That will be too long for apps to
recover and also this time cannot be influenced by any app setting. So, I prefer the solution
proposed by [~jianhe].  Please let me know your thoughts.

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