[
https://issues.apache.org/jira/browse/HBASE-19722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16464975#comment-16464975
]
Xu Cang commented on HBASE-19722:
---------------------------------
Hi [~stack] ,
Thanks.
As an experimental coprocessor, I put it as an example for now.
This targets meta table only metrics. Accessing table in the region is not
necessarily the same accessing the table's entry in meta table, this is the
reason we want to implement this.
For bad-actor, you can see I am collecting metrics per client:
"MetaTable_client_/10.9.99.3_request_count" : 23,
With this raw data exposed to JMX, people can use whatever metrics tools to
calculate topK stats. That's why I prefer not to put topk calculation to this
coprocessor since it has a performance impact on all meta table operations.
" Could we count the types of access? Thanks." – Yes, this is something I
missed. Will do.
> Implement a meta query statistics metrics source
> ------------------------------------------------
>
> Key: HBASE-19722
> URL: https://issues.apache.org/jira/browse/HBASE-19722
> Project: HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
> Assignee: Xu Cang
> Priority: Major
> Attachments: HBASE-19722.patch, HBASE-19722.patch.1,
> HBASE-19722.patch.2, HBASE-19722.patch.3, HBASE-19722.patch.4,
> HBASE-19722.patch.5
>
>
> Implement a meta query statistics metrics source, created whenever a
> regionserver starts hosting meta, removed when meta hosting moves. Provide
> views on top tables by request counts, top meta rowkeys by request count, top
> clients making requests by their hostname.
> Can be implemented as a coprocessor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
