[jira] [Commented] (PHOENIX-4276) Surface metrics on statistics collection

["Abhishek Singh Chouhan (JIRA)" <ji...@apache.org>]

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

Abhishek Singh Chouhan commented on PHOENIX-4276:
-------------------------------------------------

I can have a go if this is not being worked upon. [~vincentpoon] [~elserj] Should this be done using hbase-metrics-api for branches that support it or using hadoop-metrics2 similar to phoenix-4042?

> Surface metrics on statistics collection
> ----------------------------------------
>
>                 Key: PHOENIX-4276
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4276
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Samarth Jain
>            Assignee: Ashish Misra
>            Priority: Major
>
> It would be good to get an insight on how stats collection is doing over time. An initial set of metrics that I can think of would be:
> Time taken to compute stats (reading cells and computing their size)
> Time taken to commit stats per physical table.
> Number of guide posts collected per physical table
> Number of guide posts collected per region.
> Number of regions on which stats collection happened per physical table
> Number of times stats was collected due to major compaction vs update stats per physical table
> If possible, figure out if stats was collected because minor compaction was promoted to major compaction and surface a metric for it.
> Because most of the collection work happens on server side, one option would be to see how HBase's metrics are surfaced (my guess is JMX) and follow the same pattern. Or we could possibly use the hbase-metrics-api module but that is an HBase 1.4 thing. Another option would be see PHOENIX-3807 for some inspiration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)