Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 9 Feb 2017 23:05:41 +0000 (UTC)
From: "Billie Rinaldi (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.13041877.1486681529000.43370.1486681541951@Atlassian.JIRA>
In-Reply-To: <JIRA.13041877.1486681529000@Atlassian.JIRA>
References: <JIRA.13041877.1486681529000@Atlassian.JIRA> <JIRA.13041877.1486681529325@jira-lw-us.apache.org>
Subject: [jira] [Created] (YARN-6168) Restarted RM may not inform AM about
 all existing containers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 09 Feb 2017 23:05:47 -0000

Billie Rinaldi created YARN-6168:
------------------------------------

             Summary: 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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org