You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2017/07/12 17:45:00 UTC

[jira] [Commented] (PHOENIX-3807) Add server level metrics for secondary indexes

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

Josh Elser commented on PHOENIX-3807:
-------------------------------------

[~vincentpoon], what do you think about my last comment about naming? I can try to tweak that name and commit this today if you're OK with my suggestion :)

> Add server level metrics for secondary indexes
> ----------------------------------------------
>
>                 Key: PHOENIX-3807
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3807
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: Vincent Poon
>         Attachments: PHOENIX-3807.v1.master.patch, Screen Shot 2017-05-31 at 4.00.16 PM.png
>
>
> Add server level metrics for secondary indexes
> - Histogram metrics for time to complete all secondary index updates per primary table update per index type. Will help us trend perf over time and catch impending issues. 
> - Histogram metrics for number of updates dispatched to secondary index stores to service one primary table update per index type. Will help us catch inefficient behavior or problematic schema design. 
> - Count of deployed secondary indexes by type. Will help understand and trend index usage, or catch deploy of an unwanted index type.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)