[ https://issues.apache.org/jira/browse/HBASE-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427138#comment-13427138 ]
Hudson commented on HBASE-6399: ------------------------------- Integrated in HBase-TRUNK #3188 (See [https://builds.apache.org/job/HBase-TRUNK/3188/]) HBASE-6399 MetricsContext should be different between RegionServerMetrics and RegionServerDynamicMetrics (Chunhui) (Revision 1368354) Result = SUCCESS tedyu : Files : * /hbase/trunk/conf/hadoop-metrics.properties * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerDynamicMetrics.java > MetricsContext should be different between RegionServerMetrics and > RegionServerDynamicMetrics > --------------------------------------------------------------------------------------------- > > Key: HBASE-6399 > URL: https://issues.apache.org/jira/browse/HBASE-6399 > Project: HBase > Issue Type: Improvement > Components: metrics > Affects Versions: 0.94.0 > Reporter: chunhui shen > Assignee: chunhui shen > Priority: Critical > Fix For: 0.96.0 > > Attachments: HBASE-6399.patch, HBASE-6399v2.patch, HBASE-6399v3.patch > > > In hadoop-metrics.properties, GangliaContext is optional metrics context, I > think we will use ganglia to monitor hbase cluster generally. > However, I find a serious problem: > RegionServerDynamicMetrics will generate lots of rrd file because we would > move region or create/delete table. > Especially if table is created everyday in some applications, there are much > more and more rrd files in Gmetad Server. It will make Gmetad Server > corrupted. > IMO, MetricsContext should be different between RegionServerMetrics and > RegionServerDynamicMetrics -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira