Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 66BD6200B17 for ; Tue, 21 Jun 2016 12:57:59 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 65506160A60; Tue, 21 Jun 2016 10:57:59 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D4E32160A36 for ; Tue, 21 Jun 2016 12:57:58 +0200 (CEST) Received: (qmail 80495 invoked by uid 500); 21 Jun 2016 10:57:58 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 80474 invoked by uid 99); 21 Jun 2016 10:57:57 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jun 2016 10:57:57 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CC9A22C0451 for ; Tue, 21 Jun 2016 10:57:57 +0000 (UTC) Date: Tue, 21 Jun 2016 10:57:57 +0000 (UTC) From: "Rohith Sharma K S (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-5279) Potential Container leak in NM in preemption flow MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 21 Jun 2016 10:57:59 -0000 Rohith Sharma K S created YARN-5279: --------------------------------------- Summary: Potential Container leak in NM in preemption flow Key: YARN-5279 URL: https://issues.apache.org/jira/browse/YARN-5279 Project: Hadoop YARN Issue Type: Bug Components: nodemanager, resourcemanager Reporter: Rohith Sharma K S Assignee: Rohith Sharma K S In discussion YARN-4862 [comment|https://issues.apache.org/jira/browse/YARN-4862?focusedCommentId=15341538&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15341538], it is observed that there could be a container leak in NodeManager whenever container is preempted from RM Basically if NM receives same containerId details in {{containersToCleanUp}} and {{containersToBeRemovedFromNM}} in the same heartbeat then container will never-ever removed in NMContext. Rather NM kills the container of containersToCleanup and send back status again to RM. But RM blindly reject the status since RMContainer is already removed and it is null. I think whenever RMContainer is null, RMNode should be informed to send {{containersToBeRemovedFromNM}} so that NM will remove from its context. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org