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 870FF200B95 for ; Mon, 12 Sep 2016 11:04:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 85AAD160AB8; Mon, 12 Sep 2016 09:04:22 +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 D15E4160AC8 for ; Mon, 12 Sep 2016 11:04:21 +0200 (CEST) Received: (qmail 96577 invoked by uid 500); 12 Sep 2016 09:04:21 -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 96481 invoked by uid 99); 12 Sep 2016 09:04:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Sep 2016 09:04:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B6A562C1B8D for ; Mon, 12 Sep 2016 09:04:20 +0000 (UTC) Date: Mon, 12 Sep 2016 09:04:20 +0000 (UTC) From: "Junping Du (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-5296) NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 12 Sep 2016 09:04:22 -0000 [ https://issues.apache.org/jira/browse/YARN-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15483569#comment-15483569 ] Junping Du commented on YARN-5296: ---------------------------------- [~leftnoteasy], this is actually no need for branch-2.7 - as I discussed this with Jason on HADOOP-13362, this is just a misunderstand caused by different container remove places between branch-2.7 and branch-2. Just forget about the comment. Also, I noticed you reopen YARN-5190 for branch-2.7 which seems duplicated with HADOOP-13362. Can you double check and close it? Thx! > NMs going OutOfMemory because ContainerMetrics leak in ContainerMonitorImpl > --------------------------------------------------------------------------- > > Key: YARN-5296 > URL: https://issues.apache.org/jira/browse/YARN-5296 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager > Affects Versions: 2.9.0 > Reporter: Karam Singh > Assignee: Junping Du > Fix For: 2.9.0, 3.0.0-alpha1 > > Attachments: YARN-5296-v2.1.patch, YARN-5296-v2.patch, YARN-5296.patch, after v2 fix.png, before v2 fix.png > > > Ran tests in following manner, > 1. Run GridMix of 768 sequestionally around 17 times to execute about 12.9K apps. > 2. After 4-5hrs take Check NM Heap using Memory Analyser. It report around 96% Heap is being used my ContainerMetrics > 3. Run 7 more GridMix run for have around 18.2apps ran in total. Again check NM heap using Memory Analyser again 96% heap is being used by ContainerMetrics. > 4. Start one more grimdmix run, while run going on , NMs started going down with OOM, around running 18.7K+, On analysing NM heap using Memory analyser, OOM was caused by ContainerMetrics -- 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