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 0CCDC200CF0 for ; Thu, 7 Sep 2017 11:30:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0B73A1609D1; Thu, 7 Sep 2017 09:30:06 +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 4F2811609B8 for ; Thu, 7 Sep 2017 11:30:05 +0200 (CEST) Received: (qmail 64433 invoked by uid 500); 7 Sep 2017 09:30:03 -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 64422 invoked by uid 99); 7 Sep 2017 09:30:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Sep 2017 09:30:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0BF711A6F12 for ; Thu, 7 Sep 2017 09:30:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id li9ESsjhtola for ; Thu, 7 Sep 2017 09:30:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 5F4545FCBA for ; Thu, 7 Sep 2017 09:30:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 9A2EFE0C21 for ; Thu, 7 Sep 2017 09:30:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 50BFA2414F for ; Thu, 7 Sep 2017 09:30:00 +0000 (UTC) Date: Thu, 7 Sep 2017 09:30:00 +0000 (UTC) From: "Sunil G (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7163) RM crashes with OOM in secured cluster when HA is enabled MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 07 Sep 2017 09:30:06 -0000 [ https://issues.apache.org/jira/browse/YARN-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156734#comment-16156734 ] Sunil G commented on YARN-7163: ------------------------------- Thank you [~rohithsharma] for detailed analysis. It seems that old reference of {{rmContext}} is still not yet dereferenced when RM moved from Active to Standby. Hence when this RM moves back to Active again, we have a stale reference which have this applications reference, Nice catch. I agree with your analysis, we should not keep the reference of RMContext in services which will run with same lifetime as of jvm. > RM crashes with OOM in secured cluster when HA is enabled > --------------------------------------------------------- > > Key: YARN-7163 > URL: https://issues.apache.org/jira/browse/YARN-7163 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Reporter: Rohith Sharma K S > Assignee: Rohith Sharma K S > Attachments: suspect-1.png, suspect-2.png, YARN-7163.01.patch, YARN-7163.02.patch > > > It is observed that RM crashes with heap space OOM in secure cluster(http authentication is kerborse) when RM HA is enabled. > Scenario is > 1. Start RM in HA secure mode. Lets say RM1 is active mode. > 2. Run many applications so that it uses greater than 50% of heap space configured. Lets say, if heap space is 2GB, then run applications that occupy 1.5GB of heap space. > 3. Switch RM to StandBy and bring back to Active! While recovering applications from state store, RM crashes with OOM. > *Note* : This issue will happen only when RM is started as ACTIVE directly. (not switched from standby to active during start of JVM) > Heap dump shows that RMAuthenticationFilter holds 60% heap space! And other 40% held by RMAppState which is during recovering from state store. This exceeds the heap space and crashes with OOM. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org