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 77EB7D2F0 for ; Sun, 9 Dec 2012 01:53:22 +0000 (UTC) Received: (qmail 36427 invoked by uid 500); 9 Dec 2012 01:53:21 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 36381 invoked by uid 500); 9 Dec 2012 01:53:21 -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 36373 invoked by uid 99); 9 Dec 2012 01:53:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Dec 2012 01:53:21 +0000 Date: Sun, 9 Dec 2012 01:53:21 +0000 (UTC) From: "Adrian Muraru (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-7309) Metrics refresh-task is not canceled when regions are closed, leaking HRegion objects MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Adrian Muraru created HBASE-7309: ------------------------------------ Summary: Metrics refresh-task is not canceled when regions are closed, leaking HRegion objects Key: HBASE-7309 URL: https://issues.apache.org/jira/browse/HBASE-7309 Project: HBase Issue Type: Bug Components: metrics, regionserver Affects Versions: 0.94.3, 0.92.2 Reporter: Adrian Muraru Priority: Critical While investigating HBASE-7205 by repeatedly enabling and disabling one table having 100 regions I noticed that closed HRegion objects are kept forever in memory. The memory analyzer tool indicates a reference to HRegion object in metrics refresh-task ({{MetricsRegionWrapperImpl.HRegionMetricsWrapperRunnable}}) that prevents the HRegion object to be collected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira