You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/04/11 03:15:12 UTC
[jira] [Resolved] (HBASE-5462) [monitor] Ganglia metric
hbase.master.cluster_requests should exclude the scan meta request
generated by master, or create a new metric which could show the real
request from client
[ https://issues.apache.org/jira/browse/HBASE-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-5462.
-----------------------------------
Resolution: Invalid
> [monitor] Ganglia metric hbase.master.cluster_requests should exclude the scan meta request generated by master, or create a new metric which could show the real request from client
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-5462
> URL: https://issues.apache.org/jira/browse/HBASE-5462
> Project: HBase
> Issue Type: Bug
> Components: monitoring
> Affects Versions: 0.90.5, 0.92.0
> Environment: hbase 0.90.5
> Reporter: johnyang
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> We have a big table which have 30k regions but the request is not very high (about 50K per day).
> We use the hbase.master.cluster_request metrics to monitor the cluster request but find that lots of requests is generated by master, which scan the meta table at regular intervals.
> It is hard for us to monitor the real request from the client, it is possible to filter the scanning meta table or create a new metric which could show the real request from client.
> Thank you.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)