hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6399) MetricsContext should be different between RegionServerMetrics and RegionServerDynamicMetrics
Date Wed, 18 Jul 2012 14:54:34 GMT

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

stack commented on HBASE-6399:
------------------------------

@Chunhui Shouldn't the comments in the properties file explain why there are two hbase contexts
that can be loaded?  i.e. one does basic metrics and the hbase-dynamic adds a bunch more....
but beware, enabling it could overwhelm your monitoring as... etc.
                
> MetricsContext should be different between RegionServerMetrics and RegionServerDynamicMetrics
> ---------------------------------------------------------------------------------------------
>
>                 Key: HBASE-6399
>                 URL: https://issues.apache.org/jira/browse/HBASE-6399
>             Project: HBase
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 0.94.0
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>            Priority: Critical
>             Fix For: 0.96.0, 0.94.2
>
>         Attachments: HBASE-6399.patch, HBASE-6399v2.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

        

Mime
View raw message