You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Dave Latham (JIRA)" <ji...@apache.org> on 2013/12/05 20:37:35 UTC

[jira] [Commented] (HBASE-10089) Metrics intern table names cause eventual permgen OOM in 0.94

    [ https://issues.apache.org/jira/browse/HBASE-10089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840467#comment-13840467 ] 

Dave Latham commented on HBASE-10089:
-------------------------------------

The interning in question was already removed in 0.96 and later as part of HBASE-6410

> 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
>            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)