[
https://issues.apache.org/jira/browse/HBASE-10089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842112#comment-13842112
]
Lars Hofhansl commented on HBASE-10089:
---------------------------------------
I would still question how much memory we are actually saving. The number of
life tables will relatively small (certainly not more than 1000) and the number
of metrics per table per CF is not too large either.
> 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)
