Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 03A241075F for ; Fri, 30 May 2014 14:53:03 +0000 (UTC) Received: (qmail 46367 invoked by uid 500); 30 May 2014 14:53:02 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 46331 invoked by uid 500); 30 May 2014 14:53:02 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 46322 invoked by uid 99); 30 May 2014 14:53:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 May 2014 14:53:02 +0000 Date: Fri, 30 May 2014 14:53:02 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-11267) Dynamic metrics2 metrics may consume large amount of heap memory 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/HBASE-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013715#comment-14013715 ] stack commented on HBASE-11267: ------------------------------- bq. 1: 14917882 3396492464 [C Is pretty opaque and how the metrics instances are being retained would be good to know. Any testing done to first generate the reported condition so for sure this patch fixes it? > Dynamic metrics2 metrics may consume large amount of heap memory > ---------------------------------------------------------------- > > Key: HBASE-11267 > URL: https://issues.apache.org/jira/browse/HBASE-11267 > Project: HBase > Issue Type: Bug > Reporter: Ted Yu > Assignee: Ted Yu > Fix For: 0.99.0, 0.98.4 > > Attachments: 11267-v1.txt > > > User sunweiei provided the following jmap output in 0.96 deployment: > {code} > num #instances #bytes class name > ---------------------------------------------- > 1: 14917882 3396492464 [C > 2: 1996994 2118021808 [B > 3: 43341650 1733666000 java.util.LinkedHashMap$Entry > 4: 14453983 1156550896 [Ljava.util.HashMap$Entry; > 5: 14446577 924580928 org.apache.hadoop.metrics2.lib.Interns$CacheWith2Keys$2 > {code} > Heap consumption by Interns$CacheWith2Keys$2 could be due to calls to Interns.info() in DynamicMetricsRegistry. > This scenario would arise when large number of regions are tracked through metrics2. > Interns class doesn't provide API to remove entries in its internal Map. > Meaning, DynamicMetricsRegistry#clearMetrics() is unable to reclaim that part of heap. -- This message was sent by Atlassian JIRA (v6.2#6252)