Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9D01DF0CA for ; Fri, 26 Apr 2013 03:44:20 +0000 (UTC) Received: (qmail 77004 invoked by uid 500); 26 Apr 2013 03:44:20 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 76873 invoked by uid 500); 26 Apr 2013 03:44:17 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 76835 invoked by uid 99); 26 Apr 2013 03:44:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Apr 2013 03:44:16 +0000 Date: Fri, 26 Apr 2013 03:44:16 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642554#comment-13642554 ] Vinod Kumar Vavilapalli commented on YARN-562: ---------------------------------------------- The latest patch looks good to me, +1. Agreed about setting it to say a -ve number. +1 for doing it via YARN-618, this has become big enough already. Thanks for the testing too. I am checking this in. > NM should reject containers allocated by previous RM > ---------------------------------------------------- > > Key: YARN-562 > URL: https://issues.apache.org/jira/browse/YARN-562 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager > Reporter: Jian He > Assignee: Jian He > Attachments: YARN-562.10.patch, YARN-562.11.patch, YARN-562.12.patch, YARN-562.1.patch, YARN-562.2.patch, YARN-562.3.patch, YARN-562.4.patch, YARN-562.5.patch, YARN-562.6.patch, YARN-562.7.patch, YARN-562.8.patch, YARN-562.9.patch > > > Its possible that after RM shutdown, before AM goes down,AM still call startContainer on NM with containers allocated by previous RM. When RM comes back, NM doesn't know whether this container launch request comes from previous RM or the current RM. we should reject containers allocated by previous RM -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira