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 6AB8E1814C for ; Tue, 5 Jan 2016 00:26:41 +0000 (UTC) Received: (qmail 87954 invoked by uid 500); 5 Jan 2016 00:26:40 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 87801 invoked by uid 500); 5 Jan 2016 00:26:40 -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 87558 invoked by uid 99); 5 Jan 2016 00:26:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jan 2016 00:26:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 4714A2C1F7B for ; Tue, 5 Jan 2016 00:26:40 +0000 (UTC) Date: Tue, 5 Jan 2016 00:26:40 +0000 (UTC) From: "MENG DING (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4528) decreaseContainer Message maybe lost if NM restart 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-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082083#comment-15082083 ] MENG DING commented on YARN-4528: --------------------------------- Honestly I don't think the design needs to be changed, unless other people think differently. As you said, this RARELY, if ever happens. Also, we acknowledged that AM only issues decrease request when it knows that a container doesn't need the original amount of resource, and a failed decrease message in NM is not at all fatal (unlike a failed increase message, which may cause the container to be killed by the resource enforcement). > decreaseContainer Message maybe lost if NM restart > -------------------------------------------------- > > Key: YARN-4528 > URL: https://issues.apache.org/jira/browse/YARN-4528 > Project: Hadoop YARN > Issue Type: Bug > Reporter: sandflee > Attachments: YARN-4528.01.patch > > > we may pending the container decrease msg util next heartbeat. or checks the resource with rmContainer when node register. -- This message was sent by Atlassian JIRA (v6.3.4#6332)