hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Marc Spaggiari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10089) Metrics intern table names cause eventual permgen OOM in 0.94
Date Sat, 07 Dec 2013 11:29:38 GMT

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

Jean-Marc Spaggiari commented on HBASE-10089:
---------------------------------------------

I have some free time this WE to test it if you want. But I don't think we will see much differences.

One option is to script a loop to create/drop tables in the 2 version and compare, and for
perf, maybe something doing random tables gets with existing and non-existing names and compare?

> 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
>             Fix For: 0.94.15
>
>         Attachments: 10089-0.94.txt
>
>
> 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)

Mime
View raw message