Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 6 Dec 2013 21:29:36 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12682977.1386271892313.88524.1386365376557@arcas>
In-Reply-To: <JIRA.12682977.1386271892313@arcas>
References: <JIRA.12682977.1386271892313@arcas>
Subject: [jira] [Assigned] (HBASE-10089) Metrics intern table names cause
 eventual permgen OOM in 0.94
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-10089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu reassigned HBASE-10089:
------------------------------

    Assignee: Ted Yu

> Metrics intern table names cause eventual permgen OOM in 0.94
> -------------------------------------------------------------
>
>                 Key: HBASE-10089
>                 URL: https://issues.apache.org/jira/browse/HBASE-10089
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.0, 0.94.14
>            Reporter: Dave Latham
>            Assignee: Ted Yu
>            Priority: Minor
>
> As part of the metrics system introduced in HBASE-4768 there are two places that hbase uses String interning ( SchemaConfigured and SchemaMetrics ).  This includes interning table names.  We have long running environment where we run regular integration tests on our application using hbase.  Those tests create and drop tables with new names regularly.  These leads to filling up the permgen with interned table names.  Workaround is to periodically restart the region servers.


--
This message was sent by Atlassian JIRA
(v6.1#6144)